Errors being thrown on each token movement

[kandashi]

Errors being thrown on each token movement

[Deuterazamus]

@Arcainne while I do agree that your modifies suppress the problem at hand, I wonder how much of the code of aura.js shoud actually be executed playerside. From what I can understand of the actual code CollateAuras/MainAura are the core methods that compute everything both are bound to be executed only on the gm machine (line 321 and 405).
The code hooked on updateToken, for example, relies on what has been computed gmside in CollateAuras but will execute playerside against an empty AuraMap, thus the error.
Is it possible that all hooks should be gm only?
Are the current gm-only guards a bit too deep in the execution and could be moved up at hooks level?
I'm not nearly familiar enough with Foundry+ActiveAuras inner working so please take my suggestion with a grain of salt

[kandashi]

Yeah this is a good note, will be fixed soon

[Arcainne]

I resolved this locally by adding optional chaining to a few places in aura.js to make sure nothing is being called on an undefined object,
Before

aura.js:311:  if (!MapObject.effects) return;
aura.js:383:  MapObject.effects.forEach(i => EffectsArray.push(i.data.origin))
aura.js:502:  let checkEffects = MapObject.effects;

After

aura.js:311:  if (!MapObject?.effects) return false;
aura.js:383:  MapObject?.effects.forEach(i => EffectsArray.push(i.data.origin))
aura.js:502:  let checkEffects = MapObject?.effects ?? [];