The saddest part of all is that I got itthecyberwolfe wrote:I don't know which is worse - the fact that you said that, or that I didn't get to it firstBigO wrote:The answer to light, the macro-verse, and everything.
I need to get a life
Moderators: dorpond, trevor, Azhrei, Craig
Code: Select all
{eval(0)}
Could not execute the command: Illegal argument type java.math.BigDecimal, expecting java.lang.String
Code: Select all
{if(Rhit,' for <font> ','')}
[if(Rhit,if(Roll>=TargetNumber+4,eval(MeleeDamage)+d6e,eval(MeleeDamage)),'')]
{if(Rhit,' damage </font>','')}
Code: Select all
for »'>11 damage
Code: Select all
for 12 damage
Code: Select all
Could not execute the command: -1
My thought was to put a hidden NPC token on the map that was named End of Round. This would always sit at the bottom (in your case give it a 0 Init value) and let's me have a stopping point to take care of end of the round bookkeeping.Full Bleed wrote:...Since we roll init every round, when you get to the last pc/npc in the list and the next button is pressed to advance the round increment, the checkbox moves to the first person in the list...
Not a bad idea, but in general, players are used to rolling their inits and declaring their actions at the beginning of the new round, not at the end of the current round. It's doable, but just doesn't feel quite right.Phergus wrote:My thought was to put a hidden NPC token on the map that was named End of Round. This would always sit at the bottom (in your case give it a 0 Init value) and let's me have a stopping point to take care of end of the round bookkeeping.
Same thing can work for those playing the Hero system. Call it Post-12 Recovery.
Was the DM, perhaps, using a macro to start combat that had a remove-all (or similar) function in it? If so, it wouldn't have been a bug so much as the players jumping the gun before he could initialize the window for the new battle.UntoldGlory wrote:Did have one minor bug. During the start of one combat, myself and another player rolled init like a split second before the DM added the badguys. When he did, myself and the other player dissapeared from the list.
Someone accidentally hit their init button twice last night at one point, getting a similar lower result. As a quick fix, I just went in and manually changed their init to the first/higher roll. So, just in case it happens to you again, remember you can manually change the number and try lobbying your GM to allow it.It was poignant, cause I know I rolled a 15 the first time, and only a 5 the second, giving that annoying hexxer his turn before me...
Then how about go the other end and have a dummy token with a huge init value that stays at the top, at least in the mean time.Full Bleed wrote:Not a bad idea, but in general, players are used to rolling their inits and declaring their actions at the beginning of the new round, not at the end of the current round. It's doable, but just doesn't feel quite right.Phergus wrote:My thought was to put a hidden NPC token on the map that was named End of Round. This would always sit at the bottom (in your case give it a 0 Init value) and let's me have a stopping point to take care of end of the round bookkeeping.
Same thing can work for those playing the Hero system. Call it Post-12 Recovery.
No, cause 3 other players had already added, and they did not *poof*Full Bleed wrote:Was the DM, perhaps, using a macro to start combat that had a remove-all (or similar) function in it? If so, it wouldn't have been a bug so much as the players jumping the gun before he could initialize the window for the new battle.UntoldGlory wrote:Did have one minor bug. During the start of one combat, myself and another player rolled init like a split second before the DM added the badguys. When he did, myself and the other player dissapeared from the list.
Updatedtrevor wrote:Oops, thanks for the reminder. I usually remember, but I forgot this timeGreenMan wrote: This is just a friendly reminder (to whomever has access) to request build 41 be added to the alternate download site at
Heh... Then you could use Craig's HUGE round X ASCII art to anounce the the beginning of the round number.....Full Bleed wrote:Good call.jfrazierjr wrote:Then how about go the other end and have a dummy token with a huge init value that stays at the top, at least in the mean time.
And I have the perfect token: