RPTools.net

My group plays this way every week; my GM sends me the campaign file half an hour before game time. I open the file, start the server as a Player, and then everyone else logs in, with our GM logging in as a GM (obviously). It works fine, although obviously my GM has to trust me not to go poking arou...

This sounds very, very cool. One of the major slowdowns for my group is waiting for graphics to load every time we move to a new map. If we can just send out a graphics pack ahead of time, that will be a major help.

Added observation: It seems like if you have any map with any use of the freehand tool, this error will be present in all maps in that campaign file. Yep, you can even close the campaign where the freehand tool was used, and open an entirely different campaign (which doesn't have a freehand shape),...

Successful run of MapTool 1.3.59 on my PlayStation 3 tonight! PS3 was running Ubuntu 9.04 and Java 1.6.0 for PowerPC; game was LAN-only. I was essentially using the PS3 as a display-only client with only the map, init and chat panels open. On a vision-enabled map the PS3 did experience significant ...

I am beginning to suspect that this error has to do with using files that were created before b59. I disagree, because the problem exists (at least for me) with any campaign, even a new one that I create with b59, so long as I draw with the freehand tool first. Can you try following the steps I out...

Chrest, I had already drawn some squares in each file. In the old texture file there were squares with the error as described on the "grasslands" map. Did you find those errors when you opened it up? As I stated in my previous post, I did not see the artifacts in either the old texture fi...

I opened both campaign files, and could not reproduce the artifact with either one, despite the fact that the error showed up quite reliably for me earlier. So I started a new campaign, and couldn't reproduce the error there either. With my new campaign, I decided to check and see if the freehand is...

Confirmed on OS 10.5.8. Additionally, the artifacts disappear and reappear, and occasionally change shape, as one zooms in and out. The artifacts occur whether or not snap-to-grid is turned on, but you may have to zoom in and out to get them to appear. I think this has something to do with the way M...

Now, I have for three days now been doing all I can to host a server. I have for Port Forwarded on my router correctly linking the port number "51234" to my IP as stated in that very well written PDF document I found lurking this website. <snip> "While configuring UPnP (1) net.sbbi.u...

Confirmed on OS X 10.5.8, and some further behavior that I've noticed: whether the layout gets reset depends on the version of MapTool that is opened, not the version that is closed. For example (all closures were done with the Init panel open so as to trigger the b58 bug): b57 closed -> b58 opened:...

Okay the problem persists if you download the file from the downloads page - where you get a a .jar file. But the problem IS fixed if you download it from the webstart page - where you get a jnlp file that becomes an app file when you start it up. Awesome! The problem persists in build 58, but I ca...

And where exactly do you expect the pasted tokens to go when you select Paste from the Edit menu? Personally, I would expect it to show up in the center of my viewing window. So underneath the fog of war section that the GM hasn't cleared yet? Where auto-expose might cause the wrong area of the map...

Very weird. But I'm glad it worked for you. If other folks having this problem will post their results of trying the same thing, I'll round up the number of "aye" votes and change the web site so that it automatically includes that field... Aye, matey--the change fixed the problem for me,...

Phergus wrote:And where exactly do you expect the pasted tokens to go when you select Paste from the Edit menu?

Personally, I would expect it to show up in the center of my viewing window.

Thanks, I'll switch to <span> in the future. I tried to export the message history and check the HTML there, but the problem has magically fixed itself; I haven't modified the macro, the token or any MapTool settings since my previous post, but now everything works fine *shrug*. If it happens again,...