Problem with Multi Import - static and dynamic items - possbile enhancement

[strangealien]

Hello,

I found a problem, which is no bug, but still a problem: (UOFiddler 4.17.8, POL 0.99.1)

Consider a small house, like the houses that are already in the original multi.mul. If one imports this house from a .wsc file, it is impossible to set the flag, which decides if an item is static or dynamic. If you import it without doors and signs, you have to build this objects after the setting of the multi by hand (a GM Job, player cannot do this, but can use a deed to set the house).

If you import it in the normal way, including these objects, you have a house you cannot enter, because the door is static.

The old tool Multi_Scripter 1.1, which we used more than 16 years in the past, could do this right: It has a list of objects, which always will be dynamic. I still have this list, if you need it.

This list is the only (practical) way to import from .wsc.

There is another way: I can export our multis from the old multi.mul in CSV format, because CSV format creates entries for the flag, it is zero for dynamic parts, and one for static parts. In your code I saw (I am in no way an expert in C#, so please be patient) you always set this flag for each entry to 1 for WSC. But reading CSV or TXT format, you read it from the import file.

I tried to do it this way, and it seems to work. But it still uses information from an old import, information, it could (and should IMO) generate.

The result can be checked easily: Just modify the multi.mul, use it, and generate multis.cfg with uoconvert. You will see the parts with flag 0 as dynamic, the rest is static. (I could also edit the multis,cfg generated by uovonvert per hand, but this would be lame, and a source of bugs later).

The list I mentioned contains IDs for doors, signs and several other things.

So I propose, the UOFiddler can read and use a user provided list in some format, and it should have a default list for it.

Thank you