The other way is saving the map as an html file. It looks like this: imgur . com /fLtkbxu
The problem here is that it can ONLY be saved as an html file. It breaks links sometimes, and I don't know how to fix that if I can't save it as an image file. Plus, I don't know if I can upload html files to this site.

Anyone have any suggestions or preferences?

My worries are the following:
1. Duplication of information is always bad. Sooner or later the wiki files will become not up to date, and thus misleading.
2. Are you actually testing all information from the retro helpfiles before copying them? History shows that the helpfiles in retro are often very inaccurate, and some things are virtually impossible to test. Why copy incorrect information?

I believe wiki should contain well tested information, in particular of the kind that is not clearly explained in the helpfiles. For example quantitative description of the effects, information about non-fixed bugs etc.

Let's get RetroWIKI out of the dark ages and turn it into a useful tool.

Thanks,
Karo

The world exits interface discussion page didn't seem appropriate, so I made this new thread to talk about more general scripting stuff.

In a similar theme to the world exits I posted before, I also have almost the same script to check the time on Sosel.
It will tell you the time in Sosel hours, and also how long (in real life Earth minutes) till the next sunrise or sunset.
From what I have observed it is reasonably accurate. Again, it's a terrible hack and comments are welcome.

#ALIAS soseltime {timeprogress = 1
#VARIABLE timeobject %comcreate( "InternetExplorer.Application")
timeurl="http://70.86.15.74:3003/cgi/calendar?=fire"
#CALL @timeobject.Navigate(@timeurl)
#ECHO Looking for Sosel time…
timecheck 0}

#ALIAS timecheck {timeout=15
#IF {!@timeobject || %1 > @timeout} {#ECHO Timed out!
timeprogress=0
timeobject=0} {#IF {@timeobject.ReadyState==4} {timeprogress=0
#ECHO It is %copy( @timeobject.document.body.innertext, 24, 5) on Sosel.
soselminutes = %eval( %copy( @timeobject.document.body.innertext, 24, 2)*88+%copy( @timeobject.document.body.innertext, 27, 2))
#IF (@soselminutes < 235) {#ECHO It is %round( (235-@soselminutes)/12) minutes till sunrise.} {#IF (@soselminutes<620) {#ECHO It is %round( (620-@soselminutes)/12) minutes till sunset.} {#ECHO It is %round( (1035-@soselminutes)/12) minutes till sunrise.}}
timeobject=0} {#ALARM {+1} {timecheck %eval( %1+1)}}}}

So, I’m going to switch it to something more appropriate to reflect the ownership of that content. That will not be a copyleft licence. If there are objections or alternative suggestions to that, please comment here within the next few days or MUD mail me, send me a tell, etc.

P.S. Such matters can also be clarified on individual pages, when there is a need for that.

I’ve written a script that lets you convert the output of help skill foo in RetroMUD to the wikidot syntax and formats it like the existing pages. It’s a sed script, so if you have a Unix system (e. g. some Linux distro), you can run it. How to use: download retrowikify.sed below (click on ‘Files’ for the link) and

1. Do help skill foo in RetroMUD.
2. Copy the output, beginning with the first non-empty line after 'Help for skill:' and until the last line of the description.
3. Run sed -f retrowikify.sed | dd ibs=8192 in a terminal.
4. Paste what you copied, in the terminal. Hit enter if you didn’t copy the last linebreak. Hit ctrl-D after pasting.
5. Copy the output of the script, paste it into the edit box on the wiki and adjust as needed.

It’s faster than the description makes it sound, really, and saves a lot of typing. I’m using GNU sed, no idea if this works with others, too.

The creation of a better script is left as an exercise for the enthusiastic reader.

we’re currently using tags to connect spells and skills to guilds. Some skills are provided in a lot of guilds, which means we need to put many tags on the page, but the tag entry box has a length limit of 70 characters. For example, this is already insufficient for the bludgeon skill.

There doesn’t seem to be a server-side limit (or I haven’t noticed one yet, at least), so I’ve made a script that temporarily disables the limit. You need Firefox and the Greasemonkey extension. (I hear there’s something for Opera that does the same thing, though.)

Once you have the extension, download the attached script (click on ‘files’ below, the file is wikidotutils.user.js), drag and drop it in a Firefox window and confirm you want to install it. It’ll add an ‘unlimit tags’ button to the right of the ‘tags’ button. When you click on tags and run out of space in the text box, click the new button to disable the limit. Please use this with caution.