MapTool 1.3 Development Build 38

Post by **trevor** » Thu Jul 31, 2008 4:52 pm

Naryt wrote:Nasty token bug reported: http://forums.rptools.net/viewtopic.php?p=55015#55015

Quick summary:

If you update a token's properties via macro, no one sees the updated value until after YOU move the token. If someone else moves the token, the value is reset to what the other person was seeing.

Fortunately this is very easy to fix

BigO · Post by **BigO** » Thu Jul 31, 2008 4:52 pm

jfrazierjr wrote:
Orchard wrote:what was I saying?
Not that it's THAT hard, but we know know of yet another way to derail Orchard....

BACON!!!!

Yeah, his players know this already...

jfrazierjr · Post by **jfrazierjr** » Thu Jul 31, 2008 5:32 pm

BigO wrote:
jfrazierjr wrote:
Orchard wrote:what was I saying?
Not that it's THAT hard, but we know know of yet another way to derail Orchard....

BACON!!!!

Yeah, his players know this already...

heh..

Orchard: The goblin attacks and ....CRIT
Player: Hmmm..now where did I put that bacon??? Guys can you help me find it?
Player 2: I think it's over by the DM!
Player: I found it....munch munch...
Orchard: Now where was I? Did you guys kill the goblin yet?
Player: Yea, I critted on my long sword and he's dead.

Cweord · Post by **Cweord** » Thu Jul 31, 2008 5:37 pm

Bacon, the Bane of GM's everywhere

Orchard · Post by **Orchard** » Thu Jul 31, 2008 6:21 pm

Bacon!

It's what's for dinner!

(no, really, I have had bacon for EVERY meal today. Freaking awesome, is what that is!).

Kzintzi · Post by **Kzintzi** » Thu Jul 31, 2008 6:32 pm

Possible Bug: Tokens with the same name but different GM names don't apply SELECTED macros to the token the macro is on - they apply to the first token with the name.

To replicate: Create token A called "Fred"; create a macro in the SELECTED panel (I used {HP=HP-Dam}); give a value to the HP property; give it a GM name (eg 40); copy the token (token B); give the new token a new GM name (eg 12) but leave the Name the same as Token A (ie Fred); run the macro on Token B and it will apply the changes to token A; change token B's name to john and the macro will work on the right token

Micco · Post by **Micco** » Thu Jul 31, 2008 6:59 pm

Possible Bug: Tokens with the same name but different GM names don't apply SELECTED macros to the token the macro is on - they apply to the first token with the name.

Interesting. I'm finishing up coding some changes to the way new token's are named and I was just thinking that we should change the way we are referencing tokens. Instead of using the "public" name the way most code does now, I think it should use the "private" name (or GM name) as that is most likely to be unique.

Adopting that standard would make a ton of sense and would definitely effect how I code the new naming methods. I would force uniqueness for GM Names, but allow as many duplicate public Names as desired.

Just a thought. I'd love to hear feedback or thoughts on that as I'm finishing up the second version of the naming code this week.

jfrazierjr · Post by **jfrazierjr** » Thu Jul 31, 2008 7:06 pm

Orchard wrote:Bacon!

It's what's for dinner!

(no, really, I have had bacon for EVERY meal today. Freaking awesome, is what that is!).

heh.. my brother is like that about cheese. We had one of those "great job" parties for team I was on at work on time on a Friday with a long weekend (some holiday on Monday.) So, on Tuesday (perhaps even Wednesday) he and I were walking to my desk from a meeting and there was some of the snacks left out on a table, including cheese cubes... of course... he gobbled several down.

jfrazierjr · Post by **jfrazierjr** » Thu Jul 31, 2008 7:07 pm

Kzintzi wrote:Possible Bug: Tokens with the same name but different GM names don't apply SELECTED macros to the token the macro is on - they apply to the first token with the name.

To replicate: Create token A called "Fred"; create a macro in the SELECTED panel (I used {HP=HP-Dam}); give a value to the HP property; give it a GM name (eg 40); copy the token (token B); give the new token a new GM name (eg 12) but leave the Name the same as Token A (ie Fred); run the macro on Token B and it will apply the changes to token A; change token B's name to john and the macro will work on the right token

not a bug... don't do that. I already asked... was told no. is bad for many reasons...

Cweord · Post by **Cweord** » Thu Jul 31, 2008 7:15 pm

I don't know if this is a bug, deliberate or an item in waiting

I cant seem to call a token property that's a name from a macro - I just get asked for the number that it should be (just the content of the property)

i.e.

My property for Armour is Jacket

so I put in the code

Code: Select all

/gm
Armour = {Armour}

but then I get a question box asking the value for Jacket

Micco · Post by **Micco** » Thu Jul 31, 2008 7:20 pm

You'll need to put the text in the property in quotes (and add an extra space between the quotes and the actual letters since there <i>is</i> a bug with that.)

Example:

" Jacket " in a property called "Armor" will give:

{Armor} -> Jacket

Cweord · Post by **Cweord** » Thu Jul 31, 2008 7:25 pm

I hate it when I do that (and I have been a lot recently):

I run through testing all options, and miss a basic one, thinking I have done it.

Hopefully my brain will turn back on once the stress of getting my wife a visa is over

jfrazierjr · Post by **jfrazierjr** » Thu Jul 31, 2008 7:37 pm

Naryt wrote:
Naryt wrote:Nasty token bug reported: http://forums.rptools.net/viewtopic.php?p=55015#55015

Quick summary:

If you update a token's properties via macro, no one sees the updated value until after YOU move the token. If someone else moves the token, the value is reset to what the other person was seeing.
UPDATE

State changes also force the update. It seems to me that we need a way to force the token to update via macros to fix this. No time to go code digging though.

thats a rather big bug and may account for some things we have been seeing. I think Trevor is aware of some of this funniness, but not 100%, so hopefully, he will pipe up when he reads this....

Naryt · Post by **Naryt** » Thu Jul 31, 2008 8:14 pm

jfrazierjr wrote:
Naryt wrote:
Naryt wrote:Nasty token bug reported: http://forums.rptools.net/viewtopic.php?p=55015#55015

Quick summary:

If you update a token's properties via macro, no one sees the updated value until after YOU move the token. If someone else moves the token, the value is reset to what the other person was seeing.
UPDATE

State changes also force the update. It seems to me that we need a way to force the token to update via macros to fix this. No time to go code digging though.
thats a rather big bug and may account for some things we have been seeing. I think Trevor is aware of some of this funniness, but not 100%, so hopefully, he will pipe up when he reads this....

Yeah, very wonky.

Post by **trevor** » Fri Aug 01, 2008 12:47 am

Micco wrote:You'll need to put the text in the property in quotes (and add an extra space between the quotes and the actual letters since there <i>is</i> a bug with that.)

Example:

" Jacket " in a property called "Armor" will give:

{Armor} -> Jacket

Hmmm, good point. I don't like that. I'll see about fixing it.