RPTools.net

I've been looking into multitouch functionality for a while now (backends, etc, there's some pretty effective stuff out there) and it seems like getting the multitouch input is the easy part - the hard part is coding the interface to work with it and not be absolute rubbish, from both a design and p...

I'm seeing the same issue as Rumble in OS X - and I don't think it's possible to skip it in a reasonable manner.

EDIT: This is working now, thanks to whoever jumped in an fixed it!

Yeah, last night, he should have it. It was a really simple fix once I noticed the behavior. I'd like to thank Eclipse's Debug mode and breakpoints for letting me see the crazy-long list of token light sources that I was generating. Too bad it took me 20 minutes after that to realize that that WAS t...

@Trevor: The macro is setting it. The harolib macro sets it back to normal when it executes. This was part of the initial test, as he wanted to be able to see everything normally but target what the token can see (that's right, right?). Best I can tell the reason this doesn't work as a GM is because...

Woo, found it! This was caused because tokens don't uniquely identify sources - you had multiple torches on the token without the program displaying it any differently (making it so you couldn't tell), so every time you ran the macro and something was checked, it would add another one of it. Eventua...

This is related to the bug here. I suspected it when the last call on your trace matched the other one exactly - What I think was happening was his assigned vision type was an invalid property (old, or something) and so maptool was trying to get a nonexistent vision type as above. Having tried it on...

Turns out this was two issues - one would break if you changed a token's sight option there was no existence check), and one would break if you changed the name of the default sight assignment (it would try to default after the existence check, but would break because the default didn't exist as an ...

New to Maptool development (Hi, everyone!), started working on some bug fixes.
Working on various bug type fixes.

In Progress:
None

Patch Submitted:
1.3.b59 - Renaming default SightType name breaks vision.

I'm not seeing any macros or light sources defined in your campaign. You might have put the macros in the wrong place, though I'm not sure why the light source info is missing.