Iros means the ID of the field, not the ID of the model in the field.
Correct!
It would be better to have a Not Active When function.
This is also possible. I should really write some documentation.
However, as a short term fix/explanation:
<Conditional Folder="sewer2">
<RuntimeVar Var="PPV" Values="300..400" />
</Conditional>
...is a 'normal' conditional folder. It activates the folder when the variable PPV is between 300-400.
<Conditional Folder="sewer2">
<Not><RuntimeVar Var="PPV" Values="300..400" /></Not>
</Conditional>
...reverses the check, so now it's active only when the variable PPV is
not between 300-400.
<Conditional Folder="sewer2">
<And>
<RuntimeVar Var="PPV" Values="300..400" />
<RuntimeVar Var="FieldID" Values="213" />
</And>
</Conditional>
...combines two checks so the folder is only active when PPV is between 300-400
and FieldID equals 213.
There is also an 'Or' tag, which does what you'd expect. And you can combine them, if you really need to, so,
<Conditional Folder="sewer2">
<And>
<Not><RuntimeVar Var="PPV" Values="300..400" /></Not>
<RuntimeVar Var="FieldID" Values="213" />
</And>
</Conditional>
...activates a folder only when PPV is
not between 300-400,
and the FieldID equals 213.
Oh, that I hadn't thought of. Ok cool, how would something like that be configured? I was thinking combining this with MR may still be a good idea depending on the scene. Like in the Life Stream when there's more than one Cloud on screen in the Nibelheim memories, that way both young and present day Cloud can be used. Unless they already have separate field ID's, than just a 7H script would do the job.
As Kaldarasha said, I don't think you understand what FieldID is. It's the ID of the field location that's currently displayed, so separate models on the same screen can't have 'separate' FieldIDs. The ID doesn't belong to the model in the first place.
What you
could do is use counters, as I described for alternating battle models so you got a different battle model each time a particular enemy was loaded. It would work with field models, too.
But which scenes were you thinking of replacing models in, where the
same model is used on screen twice, and you want to replace it with two different ones?