Bug Stomp
Upgrades and changes sometimes have unpredictable results, so post your bugs and glitches in here and I'll get out my trusty wrench and get to fixin'!
Posts 4,718 - 4,729 of 8,680
Posts 4,718 - 4,729 of 8,680
Roob
20 years ago
20 years ago
I think we might need a seperate forum for Laydee to slag people off 
"Ah but the problem with that is that you, for a start, only have an honour of 579 at the moment, so you might be blocked from me," What if the levels were something more realistic like, 50 - 100, people with an honour above 50 would obviously be more serious about the forge than some 'kid from leeds' who may only ever come here once.
And stop with all the complicated words! lol

"Ah but the problem with that is that you, for a start, only have an honour of 579 at the moment, so you might be blocked from me," What if the levels were something more realistic like, 50 - 100, people with an honour above 50 would obviously be more serious about the forge than some 'kid from leeds' who may only ever come here once.
And stop with all the complicated words! lol
The Professor
20 years ago
20 years ago
BIG BUG STOMP!
Fixed a bug that was causing some (key)s to come up blank
Fixed a bug that was causing Keyphrases not to match when they should
Turned off the expectation data gathering system, which sped up the AI Engine a bunch
FengShuiGorilla: for now you cant use (mem-name) in gossip responses, because every memory referred to in gossip responses are that of the person being gossiped about.
Butterfly: The bot's name is actually "Miki's: Vanessa"
Shadyman: You can make * greedy using (re) keyphrases. But I think it would be too complicated and confusing to build into a macro.
Might have fixed a bug causing blank gossipnames to appear
Fixed a BIG bug that was causing any Keyphrase with a * but no other plug-in to always fail to match.
Fixed a problem with the username "I am" which was being marked as a name and causing mismatches in Keyphrases with "I am" in them. Improved name-recognition.
ezzer: your import bug was due to having a goto # when that seek # didnt actually exist. I've fixed it so it can deal with that now.
Ulrike: Nothing is unclickable when you enter the Language Center now.
I made further improvements to accurate name recognition.
xnomatch appears to be working now. If you are still having issues, post the part of the conversation where it happened, and point out where the xnomatch failed.
Shady: emotional range AIScript can be left in or deleted. It works either way. It's probably best to delete it as to avoid confusion.
I purged all the unconnected Keyphrases and Responses from the database. That was why the server was slow for a while, but that should speed things up a little.
Laydee: the AI Engine tries its best to change you to I or me based on the context, but its not perfect. Future upgrades will improve this ability.
Ulrike: Ill look into the (adjartnounprep) problem. Replacing them with (a|an|) (adjnoun) isnt nearly as good since the article can also include: the, my, your, our, and many others.
Fixed a bug that was causing some (key)s to come up blank
Fixed a bug that was causing Keyphrases not to match when they should
Turned off the expectation data gathering system, which sped up the AI Engine a bunch
FengShuiGorilla: for now you cant use (mem-name) in gossip responses, because every memory referred to in gossip responses are that of the person being gossiped about.
Butterfly: The bot's name is actually "Miki's: Vanessa"
Shadyman: You can make * greedy using (re) keyphrases. But I think it would be too complicated and confusing to build into a macro.
Might have fixed a bug causing blank gossipnames to appear
Fixed a BIG bug that was causing any Keyphrase with a * but no other plug-in to always fail to match.
Fixed a problem with the username "I am" which was being marked as a name and causing mismatches in Keyphrases with "I am" in them. Improved name-recognition.
ezzer: your import bug was due to having a goto # when that seek # didnt actually exist. I've fixed it so it can deal with that now.
Ulrike: Nothing is unclickable when you enter the Language Center now.
I made further improvements to accurate name recognition.
xnomatch appears to be working now. If you are still having issues, post the part of the conversation where it happened, and point out where the xnomatch failed.
Shady: emotional range AIScript can be left in or deleted. It works either way. It's probably best to delete it as to avoid confusion.
I purged all the unconnected Keyphrases and Responses from the database. That was why the server was slow for a while, but that should speed things up a little.
Laydee: the AI Engine tries its best to change you to I or me based on the context, but its not perfect. Future upgrades will improve this ability.
Ulrike: Ill look into the (adjartnounprep) problem. Replacing them with (a|an|) (adjnoun) isnt nearly as good since the article can also include: the, my, your, our, and many others.
Bowchickawowers
20 years ago
20 years ago
Nicely done, Professor! That was some serious bug stomping! I see guts everywhere, and I like it. Thanks so much.
deleted
20 years ago
20 years ago
Sonora might be upset that you mooshed up all the bugs before she could get to them!


FengShuiGorilla
20 years ago
20 years ago
Wow. You've been busy Prof.
but I don't use (mem-name) anywhere in xgossip - only (gossipname)
but I don't use (mem-name) anywhere in xgossip - only (gossipname)

alc003
20 years ago
20 years ago
Good news bad news time.
A big thank you to the professor for all the updates
However, I'm still having log-in trouble. (see a few posts back for more) Whenever I try to open a window for a keyphrase I get "I dont think so." This is random too, it worked fine earlier today.
A big thank you to the professor for all the updates

However, I'm still having log-in trouble. (see a few posts back for more) Whenever I try to open a window for a keyphrase I get "I dont think so." This is random too, it worked fine earlier today.
» More new posts: Doghead's Cosmic Bar