RPTools.net

Lemme get this out of the way up-front:

Disclaimer: This is a CUSTOM build of MapTool based on MapTool 1.3.b87, and is delivered AS-IS. Its build number is 1006. Its VERSION is "Rumble Custom VI." It is NOT endorsed by the MapTool development team, it is NOT an official build, and it is NOT supported in any way. I may from time to time issue a new version based on a more recent build.

DO NOT POST BUG REPORTS ABOUT THIS BUILD. USE AT YOUR OWN RISK.

Okay, so, that said: I've got a custom build of MapTool - it's called Rumble Custom VI - that I've made available to the GM of the game I regularly play in, but thought I might as well let other people know in case they want to use it (and in case they are "power users" who want to experiment, basically). Note: You will get a warning when loading any campaign from an official build into this, due to the version being what it is. It should not prevent proper campaign loading. If you save your campaign in this, and you can't subsequently get it to open in an official build, well...them's the breaks.

Version

I've added language to the credits to reflect that this is unofficial and unsupported. I hope that's okay.

This build offers two custom features:

Line of Sight Tool: The tool allows various kinds of line-of-sight checking. It is primarily useful on square grids. It may not work at all on hex grids (that was part of the reason it never went into the official build; I couldn't get it to work on hexes). Note that this functions like the ruler tool - it is only visible on the screen of the person using it (it doesn't show for everyone when one person uses it). To use it:

1. Select the tool and click on the starting corner.
2. Hold down Ctrl to select a single square in the target's space, Shift to select the full-size target, and don't hold down anything and you'll just get a single line.
3. You can select a different corner by going back to the starting token and selecting near a different corner. The sightlines will adjust.
4. Click on the map to clear.

Instructions also show in the status bar at the bottom, as usual.


Here are some screenshots:
LOS

Dice Window: The other item is the "dice window" (kind of a "dice calculator"). It lets you build dice expressions and then rolls them, with some very basic options, in the chat window. It's not pretty, but it does the trick. Here's a few screenshots.

Dice

You can download this build here: http://www.houseofgenius.com/files/mapt ... .b1006.zip

This is pretty neat, especially the LoS since I'm a 4e player. Would you be willing to post that patch portion of the code?

Sure. The zip file here contains the patch. Note: all of the images in the zip file go in net/rptools/maptool/client/image/tool

Maybe I just dont find it but maybe its missing: what build is this based on? I assume its b87, right? Probably a good idea to specify this somewhere...

You mean like that first sentence in the BIG RED paragraph?

Ooops

You also have that big-screaming-commercial-on-website-filter constantly active?

@rumble: nice!

Thanks Rumble!

Hi,

Is there any chance you can post an eclipse unified diff for this beautiful fork? I'm eager to integrate it in my framework

Thanks!!

I have no idea what that means. What I can offer is the patch file, which is attached 7 posts prior to this one.

That makes two of us, this is the farthest I got with it.



-Avotas

Unified Diff = a single text type file which contains a bunch of some special symbols and denote that a line number X in file Y is changed, added, or removed in the "patch". The format of the file tells the "patch" program what file(s) to change and where to make changes with in those file(s).

One thing to note here is that a patch file is not totally possible here since there are also binary elements, in the form of several new image files needed to support the LOS tool(and possibly images for the Dicebox... but I am not sure about that one)

Another issue with a diff file is that it quickly gets out of sync as the original source code changes and that could cause conflicts and broken stuff fairly quickly if the original code is updated fairly often or large changes have been made between the original diff file creation date and now.

Generally, any change made to Maptool by anyone who does not have commit access to SVN(which is very few people!!!) would require that person to create a patch file and send to someone who can commit it to SVN IF they want their updated code included into the main source code. ie, Rumble, you have done this many times before with code fixed you have donated, just perhaps used a different name when communicating with Azhrei the contents of your changes.