5E - Token Height Indicator

Quote:

---

Originally Posted by GKEnialb

We have to figure out why all of these functions keep disappearing. It is a call made from this extension, but CombatManager isn't modified in my extension. Can you give me details on your setup (other extensions, ruleset, etc?) and can you reproduce it? I can put guards around the call to prevent an error, but you can't really do much if the CombatManager goes away. Thanks.

---

I exited FGU and reloaded to see if I could duplicate the error but was unsuccessful.

Ruleset is 4e.
I have a bunch of extensions including Aura Effects.

I will mess around later with trying to recreate the error by adding extensions one at a time.

Thanks - appreciate the effort.

I've got another one for you :|
https://github.com/bmos/FG-Aura-Effect/issues/10

I wonder what is going on with these!
Perhaps see if everyone having that issue is also using Aura Effect?

I couldn't recreate locally since I can't recreate the exact conditions of the error 48. It happened during a live cloud game with four players connected. A neutral NPC with an AURA effect was introduced to the game at the beginning of the session and the error started when trying to move any character loaded in the CT and/or added later or even after PCs were changed of map or moved via Shift Drag. It really was a "close spammed logs every single token move" festival for 4 hours, but I kept quiet. No player saw the log error and I ignored it because you know, the show must go on. ^^

When moving the party token that was not linked to the CT in the Overland Map with no AURA active in that map, no error was encountered.

This is with the PFRPG1 Ruleset with these extensions:
FG-CoreRPG-Coins-Weight
FG-CoreRPG-Extraplanar-Containers
FG-PFRPG-Ammunition-Manager
FG-PFRPG-Encumbrance-Penalties
FG-PFRPG-Malady-Tracker
FG-PFRPG-NaturalArmorBonusTypes
FG-PFRPG-Time-Manager
MirrorImageHandler
Mythic-Abilities
PFRemoveEffectTag
TokenHeight
WindowSaver
Drain-and-Permanent-Bonuses
FG-PFRPG-Extra-Stat-to-Saves
FG-PFRPG-Spell-Formatting
FullOverlayPackagewithalternativeicons
FG-PFRPG-Advanced-Effects
PFRPG-EnhancedItems
FG-PFRPG-Advanced-Character-Inventory-Manager
FG-PFRPG-Live-Hitpoints
FG-PFRPG-Item-Durability
BetterMenus
FG-Aura-Effect

Quote:

---

Originally Posted by Khoredran

I couldn't recreate locally since I can't recreate the exact conditions of the error 48. It happened during a live cloud game with four players connected. A neutral NPC with an AURA effect was introduced to the game at the beginning of the session and the error started when trying to move any character loaded in the CT and/or added later or even after PCs were changed of map or moved via Shift Drag. It really was a "close spammed logs every single token move" festival for 4 hours, but I kept quiet. No player saw the log error and I ignored it because you know, the show must go on. ^^

When moving the party token that was not linked to the CT in the Overland Map with no AURA active in that map, no error was encountered.

---

Very similar experience for me as well. The only difference was a foe npc not visible was added to the CT and the errors started. Not reproducible, so far, but I will keep at it.

Quote:

---

Originally Posted by bmos

I've got another one for you :|
https://github.com/bmos/FG-Aura-Effect/issues/10

I wonder what is going on with these!
Perhaps see if everyone having that issue is also using Aura Effect?

---

The two different times this happened to me, two different campaigns. I was using Aura Effect as well as Height. It also happened an hour to hour and a half into the sessions both times.

I'll see if I get the error again with only Aura Effect loaded and not Height in our next game.

The error only happens on the GM host side, players don't see it. I had to deal with the console up every time a player moved their token for about an hour till the end of our game... as was stated earlier, the show must go on :-)

Hopefully the conflict will get worked out as Height is a really awesome extension.

I just finished some tweaking/testing on the CoreRPG Coins extension, and began receiving a very similar error. I found that all of the functions were declared as local functions, which is not what I am used to doing. So I tried changing them all from the format:

local function abc()

to

function abc()

After doing this I stopped having that error. I cant say 100% for sure this is the cause for what others are experiencing, but it may be involved somehow.

Quote:

---

Originally Posted by mattekure

I just finished some tweaking/testing on the CoreRPG Coins extension, and began receiving a very similar error. I found that all of the functions were declared as local functions, which is not what I am used to doing. So I tried changing them all from the format:

local function abc()

to

function abc()

After doing this I stopped having that error. I cant say 100% for sure this is the cause for what others are experiencing, but it may be involved somehow.

---

Actually not all of them, just the ones that only needed to be called from within that script. Using local functions is a good idea when they aren't going to be needed in another scope, but perhaps this does not work in certain circumstances such as when also using function replacement in another script (such as Token.getDistanceBetween = getDistanceBetween) or perhaps when using OOB. I've been doing the former for a while without seeing this issue, but I only just started using OOB recently so it could be that. I have globalized the functions involved in OOB messaging (but not the other local functions) for Auras v1.1-beta.2. If someone who is having this issue can give it a shot I'd love to hear your results.

EDIT: looks like I had a couple typos. here is a working test build: Auras v1.1-beta.3

I tried the Aura v.1.1-beta.2. with all my other extensions and the AURAs in the CT just stopped working altogether.
I also tried the extension alone in a new TEST campaign and no success either. Ruleset used: PFRPG1

EDIT: I tried the Aura v.1.1-beta.3 with all the extensions and everything seems to be working as intended!
I will have to try it in a live play with all the players connected, but this looks promising. ^^