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 7,003 - 7,016 of 8,681
to come up between 230 and 23:59, it gives me the message that the second time should be later than the first. ???
I went nuts with that <?PF chrono: hour(00
1-10); ?> is what I ended up with.
Posts 7,003 - 7,016 of 8,681
It's 10:40 pm server time and I notice that the Forge is running much slower than in the morning. I am also getting a bunch of xnones in short groups of three and four.
This might be a bug. When I want a message to come up between 230 and 23:59, it gives me the message that the second time should be later than the first. ???
Also, it's probably possible to jerryrig my code to outsmart this problem, but I find myself wanting to use chrono to span from, say, 11 PM to 3 AM. That means that the latter time is earlier but the next day. I'll try two chronos on the two days and see if that works, but it seems like there should be an easier way to do this. Is there?
0 and 23:59, it gives me the message that the second time should be later than the first. ???Also, it's probably possible to jerryrig my code to outsmart this problem, but I find myself wanting to use chrono to span from, say, 11 PM to 3 AM. That means that the latter time is earlier but the next day. I'll try two chronos on the two days and see if that works, but it seems like there should be an easier way to do this. Is there?
And that thing is nuts. Could we maybe have the gaping face respond only to :o or :O? The system's response to colon-zeros is messing things up all over my chronos. Or am I missing something.
thing is nuts. Could we maybe have the gaping face respond only to :o or :O? The system's response to colon-zeros is messing things up all over my chronos. Or am I missing something.
If you've just had a chat going, it takes a few minutes for the AIEngine to reset and allow another chat to start. This can be quite aggravating, because it seems that whenever I try to start a chat too soon, the time to wait starts completely over.
As for the error, two possibilities come to mind: (1) one of the bots is no longer online; (2) You've misspelled the name. I've had errors come up for both of those, though sometimes (1) just takes me to a blank screen.
As for the error, two possibilities come to mind: (1) one of the bots is no longer online; (2) You've misspelled the name. I've had errors come up for both of those, though sometimes (1) just takes me to a blank screen.
1-10); ?> is what I ended up with.
man i have been on jabbywacky and i didnt forget u guys i needed to clear my head hi prob123 pubdraught and corwin how are you today.
The Forge has been buggy all night, and sometimes I was the only botmaster on it, so it wasn't from overload, I don't think. I realize it is light in some parts of the world when it's dark here, but it usually slows down in the wee, small hours of the morning, EST/DST. I have spent the whole night and a decent chunk of yesterday working on bots (welcome Young Hamlet -- he doesn't have many non-xStatements yet, but he's a Senior at one blow). Wait 'til Rosie and Guildenstern find out about him. And I see there's some other Hamlets and Danes out there that they ain't gonna like. I'll stop making new bots before I turn into I-think-you-know-who-I-mean and try to get these to come alive someday. Then I can die happy, and I probably will, of sleep deprivation. So, thanks for talking to my bots and I will try to make them more intelligible, although I must confess the Dylan lyrics just crack me up. They don't seem to amuse the masses.
» More new posts: Doghead's Cosmic Bar