I soon realized my scripts released previously only exchange the meshes with the version fitting the Argonian Feet when equipped by an Argonian, but will never revert them back to normal, e.g. if they are taken away from the Argonian and given to another NPC or the player. Fixing this though was really easy and is already implemented and working and will be included in the next release.
I also adapted the Arena Raiment, as it is a very important armor and can’t stay an item forbidden to equip, which will be automatically force-unequipped as soon as you try to equip it.
And again I really like the results.
But working with the raiment I realized another very annoying fault of my scripts, which I unfortunately can’t fix currently as it originates from an engine glitch of Oblivion, so they might not work as expected for items having a script running on them.
Due to an engine glitch the script command “EquipItem” doesn’t trigger an “OnEquip” block in a script running on the item that gets force-equipped. The Arena Raiment uses such a script to set a flag if it is worn or not to allow entering the arena or not. Unfortunately now the script command “UnequipItem” in fact does trigger an “OnUnequip” block in a script on the item that gets force-unequipped. So when you equip the Arena Raiment, its script sets the flag to 1 (allowing you to enter the arena), then my script kicks in and force-unequips it (because it’s not a mesh fitting the Argonian Feet) and the flag is set to 0 (normal behavior up to here as expected), it replaces the mesh to be loaded to one fitting the feet and afterwards re-equips it. Now the flag doesn’t get set to 1 again as expected due to the engine glitch mentioned, which eternally prevents you from entering the arena.
There are some possible workarounds for this and one of them will be included in the next release, but only affecting the Arena Raiment for now, because I will only change the script running on it into something working more fail-safe and reliable. Later after I implemented a “global” workaround I have in mind already this will no longer be neccessary nor needed anyways.