Printable View
Looks like the latest FGU update caused an error. With only this extension loaded (5E campaign), if you cycle a monster on the combat tracker to the "None" faction, it throws:
[8/10/2025 6:02:01 PM] [ERROR] Handler error: [string "CoreRPG:scripts/manager_token.lua"]:823: attempt to concatenate a nil value
[8/10/2025 6:02:02 PM] [ERROR] Script execution error: [string "CoreRPG:scripts/manager_token.lua"]:823: attempt to concatenate a nil value
Thanks for letting me know, I'll take a look.
@GKEnialb I could not reproduce this. I tried creating a new campaign and setting the campaign type to 2024 and dropping an Aarakocra from the Legacy MM into the combat tracker and cycling it from hostile to none and back to hostile. Then I dropped a new Aarakocra Skirmisher from the 2024 MM and cycling the faction. I didn't get any errors.
I created a new campaign and set the type to Legacy and tried dropping the Aaarkocras from the MMs again and still didn't get anything.
I went back and created some encounters of both the old and end version of the monsters and added them to the tracker from the encounter and still didn't get any errors.
There have been a bunch of hot fixes and I am checking on the version released on 8/12. Try updating to that one and see if you still have a problem. If so let me know what monster you are using and how you are loading it into the combat tracker and I'll take a look.
Edit: I did do this in a 5E campaign. Are you using another ruleset?
It looks like you also have to drop the token from the combat tracker onto the map (didn't realize that until I tried to double check with a brand new campaign). So:
1) Create a new 5E campaign with only this extension
2) Load the SRD for monsters and any map
3) Drop a monster onto the combat tracker (I used aboleth since it was on the top)
4) Drop the monster onto a map
5) Cycle faction to None
I'm using this version of the extension (deleted it from extensions to make sure on update it grabbed the latest from the forge):
Attachment 65148
Thanks I'll take a lot later.
I was confused over this, but now we know about the token placement it looks like its a FG error. Still it was valuable in I did update the script file to use the updated functions, colors and variables. There was enough updated stuff I want to test it more to see if there are some horrible color combos but I should have a new version up late tomorrow.
Alright, I have released a new version on the forge and it's available now and fixes the cycling error. I was apparently sleep deprived last night about the base ruleset having a problem - it's fine. The extension needs to be refactored and I should release an update "Soonish" (TM) which should be transparent to the users. Meanwhile, if you see any weird color combos let me know.
Looks like it's working great. Thanks!