ThreadBoard ArchivesSite FeaturesActiveworlds SupportHistoric Archives |
sdk error in error codes (Sdk)
sdk error in error codes // Sdkdecastro@cable.a2000.nl (xelag)Aug 7, 1999, 10:27pm
Hi Roland,
My question as such is formulated at the end of this message :) We are testing bots to run on the WorldconVR words e_xpo and e_trek. I have been getting this message, which, if i follow the error codes (which i do), forces the bots to leave the world and stop executing their tasks: 21:09:24 VRT: vrcon503 expelled from e_xpo, reason 467 Not welcome 21:09:24 VRT: vrcon503 left e_xpo the first time i noticed this was yesterday, the 3rd bot on a multi-instance application using the same citizen number got this message, while the first 2 bots got a normal wfs message. The example I just quoted also happened during a wfs. I had two bot programs running, each using a different copy or aw.dll build 15: Delph on one, vrcon501, vrcon502, and vrcon503 on the other program. [Delph] got this message (he has a Caretaker status in e_xpo): 21:09:23 [vrcon501] exits s# 46653 at 7.5n 2.7w 4.0a 180 21:09:23 [vrcon502] exits s# 46768 at 7.8n 2.7w 4.0a 180 21:09:23 [vrcon503] exits s# 45755 at 8.0n 2.7w 4.0a 180 21:09:27 [vrcon501] enters s# 46653 at 7.2n 2.6w 4.0a 199 21:09:41 [vrcon501] exits s# 46653 at 6.4n 2.3w 4.0a 234 At the same time, the 3 bots in the other application (using one and the same citizen number, have only bot and eject rights, no enter) got these messages. The first bot got: 21:09:24 VRT: vrcon501 disconnected from e_xpo, reason 471 Connection lost 21:09:27 VRT: vrcon501 re-established contact with e_xpo, code EventAvatarAdd-54445 21:09:27 [Delph] enters s# 54445 at 0.0n 0.0w 0.0a 0 21:09:41 VRT: vrcon501 expelled from e_xpo, reason 467 Not welcome 21:09:42 VRT: vrcon501 left e_xpo The other 2 bots got a direct 467: 21:09:24 VRT: vrcon502 expelled from e_xpo, reason 467 Not welcome 21:09:24 VRT: vrcon502 left e_xpo 21:09:24 VRT: vrcon502 expelled from e_xpo, reason 467 Not welcome 21:09:24 VRT: vrcon502 left e_xpo All disconnect messages (reason 471 and reason 467) are produced by aw_world_disconnect, re-connect messages depend on which function 'detects' re-connection, in this case it was the avatar_add event. The last line, vrcon501, is a bot-program message as a result or the reason 'not welcome', and shows that all functions the bot was accoplishing have been stopped for good; a simple disconnect due to wfs does not stop the bot permanently, any other reason kills it. My question: due to the fact the bots have to work unattended and work reliably (for Worldcon VR and av99, where they will be fulfilling vital tasks), should i ignore the reason codes the sdk produces, or is there a workaround i have missed. Or, what is likely, have I mis-interpreted the enter/bots rights? bot rights give enter automatically to bots, even if they are not in the enter field. Until now i have assumed that that was the correct interpretation for all situations, but in this case I am doubting this interpretation: maybe they should be in both fields, just in case? Thanks in advance for reading and replying, XelaG. |