By Carbuncle.Nynja 2026-08-18 13:54:12
Dude probably added a spell he doesnt know in his set, or typoed a manual entry (unlikely actually possible now that I tested)
Iirc: azuresets doesnt do data validation, so it will try to set a spell you dont have even if its in the set. I remember running into problems when only half my team had a specific spell and the set wouldnt load.
just got home and tested this:
<testing>
<slot01>Subduction</slot01>
<slot02>Spiral Spin</slot02>
<slot03>Blank Gaze</slot03>
</testing>
I dont have Spiral Spin on one of my characters.
did //azuresets set testing
"AzureSets: Starting to set testing."
Removed everything I had set (including Subduction which was previously set and should be part of this set)
And is setting nothing, no error, no timeout, nothing.
<testing>
<slot01>Subduction</slot01>
<slot02>Wild Oats</slot02>
<slot03>Blank Gazed</slot03>
</testing>
All spells I have, forced a typo on Blank Gaze, same result
reload addon for fresh settings.xml
It didnt complain that there is an unknown spell in the settings.xml
//azuresets set Testing
"AzureSets: Starting to set testing"
not setting anything, no error, no timeout, nothing.
Its 100% chance an issue with the users xml file