Previous Thread
Expand All
Collapse All
Ignore Author
Reply
Ixix - look over here. http://forums.play.net/forums/GemStone%20IV/Software%20&%20Hardware%20Help/Scripting%20and%20Macros/view/249
Any word on future developments for the client?
Doug
>>I'll try to see if there's an easy way to read an .rtf file in as plain text.
Sorry, the issue is not rtf versus txt. It appears as though the MOVE script command is not waiting appropriately for the next room's output before releasing the script. We corrected to txt, and even went as far as to make each room move two lines - direction and NEXTROOM. This also failed.
So it appears that the scripting engine in Avalon isn't pausing until the right point to release (NEXTROOM or MOVE receiving the input from the new room).
Doug
Sorry, the issue is not rtf versus txt. It appears as though the MOVE script command is not waiting appropriately for the next room's output before releasing the script. We corrected to txt, and even went as far as to make each room move two lines - direction and NEXTROOM. This also failed.
So it appears that the scripting engine in Avalon isn't pausing until the right point to release (NEXTROOM or MOVE receiving the input from the new room).
Doug
Bjornsong here, my problem seems to be a general typeahead issue with Avalon...
I sometimes get the same issue if I type several commands in the command line too rapidly.
Also, many of my scripts encounter the same typeahead problem, even short scripts like the following:
</s>
<s name="l" comment="get mountain lion skin">
put kneel
put skin lion
put stand
put sheath
put search lion
put get lion skin
put put lion skin in my greatcloak
put get handaxe from my scabbard
It's not really related to scripting, but it happens most frequently when issuing multiple commands in sequence, so scripts almost always cause it.
Any ideas?
I sometimes get the same issue if I type several commands in the command line too rapidly.
Also, many of my scripts encounter the same typeahead problem, even short scripts like the following:
</s>
<s name="l" comment="get mountain lion skin">
put kneel
put skin lion
put stand
put sheath
put search lion
put get lion skin
put put lion skin in my greatcloak
put get handaxe from my scabbard
It's not really related to scripting, but it happens most frequently when issuing multiple commands in sequence, so scripts almost always cause it.
Any ideas?
Bjornsong again, just to be clear, the behavior for the typeahead issue is described here...
http://forums.play.net/forums/GemStone%20IV/Software%20&%20Hardware%20Help/Scripting%20and%20Macros/view/267
http://forums.play.net/forums/GemStone%20IV/Software%20&%20Hardware%20Help/Scripting%20and%20Macros/view/267
Stormfront has some quasi-baked in RT and pacing things. So when I was using Avalon, I had to use pauses a lot more than I ever did in SF.
---
Rohese: "... the TownCrier (tune in if you haven’t, it’s without doubt the best thing to ever happen on LNet)"
;tune towncrier
TownCrier News Submission link: http://bit.ly/TownCrierNews
TownCrier News Dailies via Email: http://bit.ly/2ivAJfw
---
Rohese: "... the TownCrier (tune in if you haven’t, it’s without doubt the best thing to ever happen on LNet)"
;tune towncrier
TownCrier News Submission link: http://bit.ly/TownCrierNews
TownCrier News Dailies via Email: http://bit.ly/2ivAJfw
In my view, there are some commands in scripting that are intended to not require repetitive maintenance from the script writer, like MOVE.
However, there is also a responsibility on the part of the script writer to understand the environment they're in (number of concurrent requests to the system, or 'typeahead') being one of the leading elements. Then that script writer is responsible for ensuring overrun doesn't happen. Likewise, the script writer is responsible for determining success / failure of the command and building out the script response in the event of failure (the system informs, the script acts).
All of which is a fancy way of sayin', 'no matter what, MOVE and NEXTROOM are broked, yo'.
Doug
However, there is also a responsibility on the part of the script writer to understand the environment they're in (number of concurrent requests to the system, or 'typeahead') being one of the leading elements. Then that script writer is responsible for ensuring overrun doesn't happen. Likewise, the script writer is responsible for determining success / failure of the command and building out the script response in the event of failure (the system informs, the script acts).
All of which is a fancy way of sayin', 'no matter what, MOVE and NEXTROOM are broked, yo'.
Doug
