NOTE: The 'map' command has been changed to 'lmap' in the mapper module, to avoid conflicting with the in-game command.

I've made several tweaks, fixes, and enhancements to this LMTS. It comes without a map, and it should be 100% compatible with your current LMap, if you have one built already. It also comes without any ILua scripts, and your old scripts may not be 100% compatible with this version.

I do all my development for LMTS using the MinGW compiler on Windows. You're on your own for compiling it on other platforms, but you shouldn't have too much trouble getting it to work.

Look at the ChangeLog.LMTS to see a list of what changes I made and what's on the todo list yet. Post your questions, comments, etc on this thread. Please do not send me messages about LMTS in the game. Thanks.

Source files without binaries
Windows binaries for a wrapwidth of 80 columns
Windows binaries for a wrapwidth of 0

Disclaimer: Use at your own risk, yada yada yada.


(Edit: the links are now 404 because I removed the files. Sorry!)

If compiling the source files ourselves - which version is that? 80 or 0?

The makefile is configured for the 0 wrapwidth, by default. To compile the 80 wrapwidth version, remove the "-DNOWRAP" compiler option.

I'd like to note map doesn't get in the way. I type "maps" on Lusternia to see their's. However to me it doesn't matter, I'll just setup an alias that allows me to remain using map.

instead of changing to lmap... MAP vs map worked, you know :/

A. Even if MAPS works the same as MAP in Lusternia, it's not the given syntax and I'm not going to be blamed for overriding it.

B. I didn't realize the commands were case sensitive, but I really don't want to just tell people to use all caps to bypass the LMTS mapper command. What I should do, actually, is make the LMTS commands case insensitive now...

C. You're free to change the source and compile your own version.

All caps isn't a bonus, having to press and hold shift while typing map, or using caps locks is more of an inconvenience than using maps.

Anyways! It doesn't matter! An alias will fix it up to be whatever I want. If anyone has problems making their own alias to do the same, then they should just get off of the MUD!

I'm glad to see newer versions coming out. I really need to utilize LMTS more and my own client less, but I just get sidetracked into doing other things, and my client is so much faster to setup when I need something. I'll get around to it eventually..

Another word of caution: your old LMap/IMap file (built with 80 wrapwidth, presumably) will not work 100% with the nowrap version of this new LMTS. You'll need to update the triggered special exit messages to include the entire text, as LMTS only captures the last line of a special exit message.

How would we go about doing that? I currently use Shamarah's map (with LMTS), want to use the 0 wrapwidth version of the new LMTS.

Can the wrapwidth concept be explained? I'm not certain yet on what it means, and how it would affect anything.

You would open your LMap/IMap in your favorite text editor and update the messages. You'll have to shutdown MudBot and restart it after your edits are complete. The inline map load function has been broken for quite some time, and neither Whyte nor myself has been able to fix it.

For global special exits, I have mine setup in such a way that they should work for 80 or 0 wrapwidth. I use wildcards, like so:


For room special exits, you need to do a similar thing, except that I don't use wildcards for mine. Search through your file for the "SPE:" and you'll see the partial lines that you need to update.

The game's default is 80, and that determines where words wrap in your client. The server adds linebreaks after roughly 80 characters in any long message, such as room descriptions, warrior attacks, etc. You may have noticed that you can size your client window as wide as you like and the text remains wrapped at the same place.

The newer 0 option (CONFIG WRAPWIDTH 0) prevents the game from adding any of these extra linebreaks, and instead it allows your client to take care of the word wrapping. This option makes it much, much easier to build triggers on those long messages because you don't have to account for variable linebreak positions.

Seems simple enough. My only other question relating to the mapper - should I be using the lmapper version included in the last imts or the imapper I compiled in this lmts?

The i_mapper.dll in this release is the one I modified heavily to improve functionality in Lusternia. That's the whole reason I did this, so it'd be a shame to waste it. Yeah, I just didn't get into renaming the module this time... Sorry for the confusion.

Hmm, did you remove some options?

Listening on port 3000.
Loading file './i_mapper.dll'.
ATCP passthrough enabled
LMap loaded. (141677 microseconds)
Parse error in file 'config.mapper.txt', unknown option 'Disable-WhoList'.
Parse error in file 'config.mapper.txt', unknown option 'Disable-Alertness'.
Entering main loop... All ready.

Yes. Alertness doesn't exist in Lusternia and the WhoList location stuff isn't coded in LMTS because we don't have the same sort of WhoList they have in Imperian. Those parse errors are more like warnings, but you can remove the lines from your config.mapper.txt file to get rid of the messages.

For some reason my mapper isn't tracking what room I'm in.

Map is loaded, as shown by..

7590h, 7920m, 7590e, 10p, 32400en, 33900w esSilrx<>-|FREE|On!|PAUSED ME|lmap status


Rooms: 9508, using 3308784 bytes of memory.
Areas: 129, of which fully mapped: 112.
Room structure size: 348 bytes.
Hash table size: 512 chains.
Map size, x: 14 y: 10.
Room title color: unknown, code length 5.

Why does it say 'Room title color: unknown' I wonder? Are you using 'Title-Color brown' (or whatever color name matches your setting in the game) in your config.mapper.txt? At any rate, I'd say that's the source of your troubles there.

What I have in my config is the following:

# File generated by LMapper.# Manual changes that are not loaded will be lost on the next rewrite.Title-Color brownDisable-Swimming yes#Disable-WhoList no#Disable-Alertness noDisable-Locating noDisable-AreaName noDisable-MXPTitle noDisable-MXPExits noDisable-MXPMap noDisable-AutoLink noDisable-SewerGrates noEnable-GodRooms no# Room Tags.

Wrapwidth 0 version causes a segmentation fault error and crash of mudbot. Any reason why/how to stop this without not using wrapwidth 0?

Crashlog: