I'am not quite sure if i understood you correctly.
I gave an example on how i think it could work. That's always the best way.
One of our scripters writes a tool to read/write multi.mul files.
This tool writes all multis into a readable text format or writes a new multi.mul from these text file/s.
With readable i mean:
Multi xxxx
{
Item1 color x y z objtype specialflags/options
Item2 color x y z objtype specialflags/options
.....
}
Just to give an example in this case of a multi mul.
So if i understand you right, it would be great if such a module can read e.g. staticN.mul and write it to a readable text format like above.
Every Pol scripter then has the opportunity to change these files with custom own written Pol commands like we do with the multis.
For statics this could be e.g. search all items of objtype xx in area nn to mm and delete them/set them 1z up/if(... do ...) and so on.
After changes made and a new text file is written the module should recompile it in this case to a new staticsN.mul and the staidxN.mul
I think this can be done for every mul. It perhaps sounds complicated, but the possibilities are wide open cause this way you can customize it. To stay at my first example, we can read a e.g. sphere .wsc file or a UO Architect File or whatever into Pol (custom scripts). Check that multi in this case single items, save or edit it and rebuild the multi.mul/idx.
Hard to explain, i hope it sounds not to weird
