The Aaron said: The issue is that the 5th Edition OGL Companion inspects the value of the bars to determine which one is used for HP. It checks them in numeric order, so finds bar 1's 11 first and determines that must be the HP, so sets it to the new value. The next time you run it, it finds the 11 in bar 3 and so changes that one. The 3rd time, there are now bars that have 11, so it does nothing. I don't actually know anything about this script, other than what I just tracked down, but this seems like a bug in the method chosen for implementation. Right, my experience too. I have my tokens set up with HP in bar 2 and AC in bar 1. The scripts seems to fail always if AC = HP (avg). E.g. Derro have AC 13 and HP 13. If I use !npchp on them, the AC is randomized and becomes a bar instead of HP. I also had sometimes the issue that the script then crashed with some error messages. Problem is: how should the script know what the HP are (since for monsters these are not linked in the toekn)? I see only two ways: Look not only for the value == HP (avg), but also if there is a max values set (which is of course not for AC). Look into the Game Default Settings (where I set up that AC is bar 1 and HP is bar 2). The least error-prone solution seems to me the first one, since the Game Default Settings are a fragile thing :-) Who is responsible for the script? Is it possible to address him/her somehow? Because it's an awesome feature and I really would like to use it in my campaigns. And by the way: if the script would not look at HP(avg) at all, but only whether there is a bar with value = max and randomize this, you could run the script multiple times on the same tokens - which is currently not possible, because after the randomizing it can't find a bar with the HP value anymore. This would just bad for people using a bar for a different attribute with value = max (e.g. temp HP or something). But I think that is a rare case.
