RPTools.net

I think this may turn out to be a bug, but I'm posting it here just in case I'm missing something. My D&D 3.5 character has the following attack macro, which performs a check for a critical threat and then re-rolls the attack to confirm. <b>Longsword:</b><br> Attack Roll: [t: attackRoll = 1d20]<...

I'm sure we're not the first to do this, but MapTool was incredibly handy the past few months, as it allowed me to continue playing with my D&D group, despite the fact that I spent most of the summer in India. We had already been using MapTool because the members of our group live in three diffe...

Borked for me too on 10.5. I don't really know much about JNLP files, but after a quick perusal of the Sun JNLP syntax page, it appears that <j2se version="1.5+" initial-heap-size="64m" max-heap-size="512m"/> is an alternate way to specify memory allocation; perhaps thi...

This bug only occurs when both Fog-of-War and Daytime vision are enabled, and a token with vision has revealed some areas of the FoW. If you zoom out far enough, the medium shading denoting "revealed but not visible" becomes progressively more misaligned with the shading denoting "vis...

If I am missing a step, let me know, but otherwise, I can't reproduce this. I'm running Mac OS 10.5.7 and the latest applicable version of Java. I also can't reproduce using the b56 release. If it is the "bazillion extra lines of geomerty" (I've only just skimmed this thread) bug, the map...

The thing that baffles me is that it doesn't make sense to me why it would be a problem. Scale is just that ... scale. It shouldn't necessarily require more work. So I'm not convinced it's the size of it that matters. Can anyone confirm that it goes away for them by reducing the default vision dist...

The thing that baffles me is that it doesn't make sense to me why it would be a problem. Scale is just that ... scale. It shouldn't necessarily require more work. So I'm not convinced it's the size of it that matters. Can anyone confirm that it goes away for them by reducing the default vision dist...

I agree with you that dragging tokens around does cause objects to be created, but I can't replicate the behavior you're reporting. If I drag a group of tokens around for long enough, MapTool uses more and more of the heap. However, when the heap limit is reached, the garbage collector kicks in and ...

It looks like it's the auto-save function that is causing the problem. It creates a copy of the entire campaign so that the auto-save thread can then run concurrently on the copy without synchronization issues. However, this means that for a large campaign file, everything shuts down while the copyi...

I've been acting as the host for my gaming group, and I have noticed that periodically, my copy of MapTools freezes while hosting. The duration of the freeze and the period between freezes appears to depend on the number of tokens on the current map; it doesn't seem to correlate to user activity. Th...

I made the same mistake when I wrote my first macro. Perhaps "Short name" should be changed to something more descriptive?

If we're going to futz with Applescripts, might it not make more sense to simply package the .jar in a .app? I just tried this out, and it works great--much better than my Applescript! This gets my vote for a Mac-friendly distribution format, and it looks like it can be entirely or mostly implement...

As a possible solution, I've hacked together an Applescript that does approximately the same thing as the shell script does now (it doesn't handle multiple versions of MapTool, however). Since script files are executed from within Script Editor, this should avoid the issue with permissions and .zip ...

cd "$PWD" (When I tested it just now by double-clicking a script from Finder, the PWD variable contained the correct directory, so no need to create a new one. :)) That's not what I'm seeing--when I add echo $PWD to the top of the script, it outputs "/Users/myusername" regardles...

I also encountered all of these problems, and fixed them the same way. Here's my solution to Issue 3; it's basically the same, except it doesn't use dirname.

dir=${0%/*}
if [ "$dir" = "$0" ]; then
dir="."
fi
cd "$dir"