MapTool 1.3 Development Build 45

Post by **trevor** » Tue Sep 23, 2008 6:28 pm

The "Apple bums me out" build

* This is a rebuild of 1.3b44 using java 5 instead of java 6

Orchard · Post by **Orchard** » Tue Sep 23, 2008 6:37 pm

trevor wrote:The "Apple bums me out" build

* This is a rebuild of 1.3b44 using java 5 instead of java 6

B44, OH where did you go?

This may be a record for the SHORTEST lived build...

I'm guessing that 99% of the users will have not even seen the announce for b44 by the time this announce has gone up.

It's funny, but still sad.

Orchard · Post by **Orchard** » Tue Sep 23, 2008 6:38 pm

And it's launching from the web for me...

Excellent!

Post by **trevor** » Tue Sep 23, 2008 6:40 pm

Orchard wrote: Excellent!

Indeed

Mithrus · Post by **Mithrus** » Tue Sep 23, 2008 6:49 pm

I already downloaded 44...lol

Post by **trevor** » Tue Sep 23, 2008 6:54 pm

Mithrus wrote:I already downloaded 44...lol

If it works for you then great, b45 is the same thing, just built with with java 5 instead of java 6

toyrobots · Post by **toyrobots** » Tue Sep 23, 2008 7:24 pm

Thanks for going through the trouble Trevor.

I would be very sad to miss out on the tool just because of my OS preference.

Testing: Lighting bug is fixed.

Macro redraw bug is fixed.

Looking good so far. My campaign macros appear to have vanished. Any suggestions?

PyroMancer2k · Post by **PyroMancer2k** » Tue Sep 23, 2008 8:55 pm

This was a bug in previous versions as well.

When you create a new token the default values don't get set on the token until you open it. Normally this is a manageable problem by quickly opening the token. But for tokens that have Variables like say FORT with a default value that calculates something like {10+StrBonus} for the statsheet then when you move over the token it creates a dialog popup that is empty. If you have a lot of values calculating on the statsheet this creates a ton of dialog boxes so that you have to close MT down with task manager.

Each unset variable creates several dialog boxes. For a test I put *@AC:{Test} as default value and then made a token. It created several dialog boxes that I had to close for that one unset variable.

Orchard · Post by **Orchard** » Tue Sep 23, 2008 9:02 pm

PyroMancer2k wrote:This was a bug in previous versions as well.

When you create a new token the default values don't get set on the token until you open it. Normally this is a manageable problem by quickly opening the token. But for tokens that have Variables like say FORT with a default value that calculates something like {10+StrBonus} for the statsheet then when you move over the token it creates a dialog popup that is empty. If you have a lot of values calculating on the statsheet this creates a ton of dialog boxes so that you have to close MT down with task manager.

Each unset variable creates several dialog boxes. For a test I put *@AC:{Test} as default value and then made a token. It created several dialog boxes that I had to close for that one unset variable.

Try opening it via the map explorer? At least until the bug-fix comes around!

lmarkus001 · Post by **lmarkus001** » Tue Sep 23, 2008 10:18 pm

PyroMancer2k wrote:This was a bug in previous versions as well.

When you create a new token the default values don't get set on the token until you open it. Normally this is a manageable problem by quickly opening the token. But for tokens that have Variables like say FORT with a default value that calculates something like {10+StrBonus} for the statsheet then when you move over the token it creates a dialog popup that is empty. If you have a lot of values calculating on the statsheet this creates a ton of dialog boxes so that you have to close MT down with task manager.

Each unset variable creates several dialog boxes. For a test I put *@AC:{Test} as default value and then made a token. It created several dialog boxes that I had to close for that one unset variable.

In B43 just opening the token was insufficient. I would have to open, and click on each property element to get the defaults to hold.

Same behavior is occurring in B45.

BUG

Set your campaign properties to:

Code: Select all

Level:1
Dexterity (Dex):10
DexMod:0
Constitution (Con):10
ConMod:0
DexB:{floor((Dexterity+DexMod-10)/2))}
ConB:{floor((Constitution+ConMod-10)/2))}
*@HPmax:{0 + (ConB * Level)}
Initiative:0 + DexB

Now drop a graphic onto the map to make a token, then try to mouse over that token. You will get an Input box that does not fully form.

This is a default properties issue. If you then Edit and left click on the Constitution property then click OK, that property will actually become live and all will be ok.

http://forums.rptools.net/viewtopic.php ... c&start=62

BigO · Post by **BigO** » Tue Sep 23, 2008 10:22 pm

Wow, that was quick.

PyroMancer2k · Post by **PyroMancer2k** » Tue Sep 23, 2008 11:37 pm

Orchard wrote: Try opening it via the map explorer? At least until the bug-fix comes around!

Yea I about this work around just reporting it in hopes it gets up on the next update list

. Can it's kinda annoying having to be real careful each time I create a new token.

Post by **dorpond** » Wed Sep 24, 2008 10:06 am

I used B45 during my face to face game last night (5 laptops) and it worked like a charm. The players really enjoyed the new Health Bars (thanks Jay). I didn't get a chance to send my DM the updated state overlays so next week will be even more exciting!

Thank Trevor for going out of your way yesterday to make a solid build. Much appreciated!

wrathchild · Post by **wrathchild** » Wed Sep 24, 2008 11:59 am

Health bars: Mine are still red. Top Down tokens.

I would like to have the option to put them at the bottom of the token. Is that something that is considered?

BigO · Post by **BigO** » Wed Sep 24, 2008 12:10 pm

Trevor, do you have a feel yet for when we might pull the plug on 1.3 and start into 1.4?

RPTools.net

MapTool 1.3 Development Build 45

MapTool 1.3 Development Build 45

Re: MapTool 1.3 Development Build 45