MapTool 1.2 Development Release Build 25

[trevor]

The "Oops, I did it again" release. Tweak tweak tweak:

Build 25 (4/24/2007)
* Revert hex grid angle adjustment (oops)
* Re-enable Enable Fog and Hide Map shortcut keys (*waves to phergus*)
* Update "Zone is not visible to players" to "Map is not visible to players"
* Change "Expose->Player visible area only" shortcut from CTRL-O to CTRL-SHIFT-O
* Revert some bad debug code that broke vision and fog

Please let me know right away if any of these are still problematic and I'll make more tweaks, and more builds

[Jaxal1]

The "Oops, I did it again" release.

*shudder*

[dorpond]

Is it me or does Control-Shift O not work?

It covers up the FOW but for me it doesn't reveal the vision of the token selected. *shrug*

[trevor]

Is it me or does Control-Shift O not work?

It covers up the FOW but for me it doesn't reveal the vision of the token selected. *shrug*

Did you make sure the token is a PC or player owned ?

[dorpond]

OK that did it..

Question though: Why is ownership manditory when using Control Shift O but it doesn't matter when using Control I or Control P? Just curious is all..

[edit] Scratch that question. I see now that the only way MT knows who the "party" is is by designating PC ownership. This way the whole party shows vision when doing Control Shift O.

[trevor]

Question though: Why is ownership manditory when using Control Shift O but it doesn't matter when using Control I or Control P? Just curious is all..

Because I and P both have an explicitly selected token to operate on. But the Expose Visible Area Only has to look through all tokens on the map and figure out which ones are part of the party. So there has to be a designation which token's vision to include, that designation is PC or player owned (these two concepts will be merged soon)

[dorpond]

So far no hickups.

[trevor]

So far no hickups.

*whew*

[dorpond]

Not sure if this cropped up recently but when I drop a token named "TikiMan3" onto the map, rename it to "TikiMan 2012" and copy/paste it, it names it TikiMan 2012 2 (adding an addition number to it) instead of incrementing it.

Actually I am getting some really strange behavior now the more I play with it. All I know is that it isn't working the way it used to every week that I play.

Did something go south now that we have the auto copy feature?

[trevor]

Did something go south now that we have the auto copy feature?

Tell me more about the weirdness you are seeing, and I'll let you know

[dorpond]

Well let me ask you this; if I have a token named Tiki 2156, copy/paste it, shouldn't the next one be Tiki 2157?

That's the way it was last weeks game anyway. I will load up an B23 and verify.

[Maruz]

Hello hello

I tried to use the "/rsec" feature, and typed "/rsec Intimidate [1d20+6]" Then the DM got this response:

* Marius rolls secretly to you: [roll 1d20+6 => 10 + 6 => 16] => Invalid expression: [roll 1d20+6 => 10 + 6 => 16]

What's up with the Invalid expression thing?

[trevor]

I tried to use the "/rsec" feature, and typed "/rsec Intimidate [1d20+6]" Then the DM got this response:

* Marius rolls secretly to you: [roll 1d20+6 => 10 + 6 => 16] => Invalid expression: [roll 1d20+6 => 10 + 6 => 16]

What's up with the Invalid expression thing?

Ahh, right. The problem is that /rsec was implemented before inline rolling. So it doesn't know about how to parse the line. It expects something like /rsec 1d20+6. So it's doing its best, but isn't quite making it.

What I need to do is update the roll macros to understand and use the new inline rolling so that you can have labels.

In the mean time you can do something like:

/th Intimidate [1d20+6]

The "/th" is "/think" which only sends the result to you.

[dorpond]

Well let me ask you this; if I have a token named Tiki 2156, copy/paste it, shouldn't the next one be Tiki 2157?

That's the way it was last weeks game anyway. I will load up an B23 and verify.

OK, I got the scoop. I recently started using 1.2 for our games on Tuesday nights. Most of my campaign material was made with 1.1 that I converted over to 1.2.

In 1.1 the copy and paste worked properly but in 1.2 it does no increment the right way. If I name a token "monster 2456" and I copy and paste it, it should increment to "monster 2457", "monster 2458", etc.. Instead, it is adding a 2, 3, 4 after the name of the monster so we end up getting "monster 2456 2", "monster 2456 3", etc..

This isn't really a 1.2B25 bug but I wanted to explain what I found since it cropped up here.

[trevor]

This isn't really a 1.2B25 bug but I wanted to explain what I found since it cropped up here.

That's what I was expecting, whew. I'll add a tracker for that bug