Cool.Vadi wrote:On IRE games, nothing. Though with the upcoming expansion to ATCP, some commands seem to have been added but they aren't documented (decompiling the Nexus client will find you some).
So the server just sends everything to the client, even if the client doesn't care about it?Vadi wrote:On IRE games, nothing.
I was wondering how the server was supposed to know which variables to send, I guess that explains it. I could see this becoming a problem as more variables are added, but at least the Mudlet implementation seems to be flexible enough to handle my workaround.
Not quite, during the negotiations the client asks which data sources to enable. For Mudlet, it's currently hardcoded to all popular IRE ones (but this will need to change soon to be scriptable/configurable, for one we're missing one option already...)
ATCP events definitely work fine - at least there are no known issues whatsoever. As your MUD is going to be included on our recommended MUD list this issue should be fixed. Please send me your script and a test account on your server by email.KaVir wrote:My attempt at adding events broke the script entirely, but at least its working from the server side.
I don't mean Mudlet doesn't work, I mean I'm struggling to understand Mudlet scripting, and therefore can't provide a visible demo as proof of concept - but it should now be usable for someone who knows what they're doing.Heiko wrote:ATCP events definitely work fine - at least there are no known issues whatsoever.KaVir wrote:My attempt at adding events broke the script entirely, but at least its working from the server side.