You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't urgent to fix, I only found this problem with one line of my VDF, so I just fixed that line for now.
However if the value for a key is on a separate line, the parser gets very confused.
I was running multiple parses and the data was getting entrenched further and further with each run. It wouldn't reset to a normal state until I restarted the node server.
The "Attributes" key is followed by the "MODIFIER_ATTRIBUTE_MULTIPLE" value on the next line. (this data still compiles/runs successfully inside of dota2
I was parsing my ability file, followed by my units file
var abilityData = vdf.parse(abilities_file);
var unitData = vdf.parse(units_file);
abilityData was the one that was causing the issue, but when i ran console.log on my units file, it added "DOTAAbilities" and "item_apply_modifiers". Each additional time I ran my parsing function, it added additional depth to the units file...
This isn't urgent to fix, I only found this problem with one line of my VDF, so I just fixed that line for now.
However if the value for a key is on a separate line, the parser gets very confused.
I was running multiple parses and the data was getting entrenched further and further with each run. It wouldn't reset to a normal state until I restarted the node server.
The "Attributes" key is followed by the "MODIFIER_ATTRIBUTE_MULTIPLE" value on the next line. (this data still compiles/runs successfully inside of dota2
I was parsing my ability file, followed by my units file
abilityData was the one that was causing the issue, but when i ran console.log on my units file, it added "DOTAAbilities" and "item_apply_modifiers". Each additional time I ran my parsing function, it added additional depth to the units file...
hope this all makes sense, let me know if you need some more information
The text was updated successfully, but these errors were encountered: