Just for info, we have a simple version ready, if you would like to take a look at our mapper.xml

https://github.com/Kebap/krrrcks-mudlet

Now for eliminating all the usability issues and writing a concise description for newbies.

I asked about related issues in my thread here: import lua? For the XML structure, just create a few scripts, timers, etc. via the Mudlet GUI. This seems to be the recommended way for most users. You can then export a package and look at the XML structure. I never bothered writing XML from scratch, ...

Half a year later maybe somebody got a few minutes?

Oh well, it seems like there is no simple solution (yet) to this simple request. I assumed otherwise. So the smartest thing seems to me, creating a new function for saving the player's inputs. At best, to the same file as the mud's output. Maybe there already are some scripts with alike functionalit...

A friend asks, is there an easy way to save to logfile also the player's input and not just the output from the mud?

I have run into these English strings in the mapper API before, and it is really a PITA if your MUD does not send English strings to compare with. An easy solution would be to add a way for scripts to overwrite the accepted strings. Translation tables seem more complicated. If you can already ship t...

Seems like this issue is still open. Should be easy to fix, albeit only few people have the necessary rights.

I am not sure I understand your answers correctly, so I will clarify again: When I first connect to the MUD, everything is fine. I can enter my char's name in the same line as the question prompt. This is deliverately so. Only when I connect again, I see a different behavior. Also, I only see it whe...

Ok sure, I can use gmcp and build a script, which would draw the current room on map, and include all known exits, draw them as stubs. Not sure, how exactly the code will look, but seems possible. Then I move to another room. Now I get the visible exits, directions from this room. But gmcp does not ...

What I did already: * Created a room manually, created another room manually, linked them via exits manually (unfortunately, that is where the mapper tutorial ended) * Create a GMCP script, which will be executed, whenever any new room is entered. It then goes on to save the room's id to a list, or ...