The Engine/Editor's Greatest Weakness: Location Slots

[paradigmblue]

In modding WitP:AE, the most limiting factor is the lack of location slots.

These location slots not only determine base locations, but are also used for all LCUs. For mods that want to add more units and locations to the game, it is very easy to start running into a lack of slots that prevents you from adding everything you want.

Is there any way around this limitation, or any way to mod the editor/engine itself to add more location slots?

[wdolson]

The location slots was expanded for AE because the original WitP was limited. Unfortunately it can't be expanded by an end user. It could be expanded in code, but it would require a number of changes throughout the code to support any expansion and it would also slow down the game. The bigger the tables the longer the searches of the tables.

Bill

[John 3rd]

I wish there were large blocks of open space for a Modder to place ALL their work in the files. All new ship classes together, new aircraft together, etc... It would certainly help with building a Mod and KNOWING WHERE one put what...

[Dili]

The biggest limitation i found in editor is the lack of being able to write notes explaining the decisions. Ideally the editor should be linked to a database of conflict.

[cardas]

How about the painful experience of trying to move things around; want to change those ship classes from using slots 7001-7100 to 7000-7099? Congratulations! Now have fun fixing all the "Upgrade" IDs to match and also correcting every single ship that uses any of those classes.

What makes it frustrating is that the editor is almost there, but not quite, ultimately making it easier to use witploadAE in many cases.

Comments and more slots overall would help. I can accept the slot limit as an engine optimization issue though.

[Dili]

That too.
Optimizing the database units, devices filling the slots with some logic to find things easier, you can't do it if you have things already interconnected . If you have the gun XX in slot YY you can't change it if is already in some ship. So basically the building the database must be made in one go. The other option is to not care for its logic.

[LargeSlowTarget]

ORIGINAL: paradigmblue

In modding WitP:AE, the most limiting factor is the lack of location slots.

I feel the pain, bro. I have scavenged base slots from less-active and seldom-used bases to turn them into something more useful (no one will miss Tonopah, no?) and simplified the seldom-activated Russian OOB in order to free slots for other units. I think I have one or two empty slots left.


That triggers a question - is it necessary to keep a reserve of empty slots to allow units in-game to split?

[wdolson]

I haven't looked at it in some time, but I believe there is a section of the location table the editor has no access to that is used for split units.

Bill

[PaxMondo]

ORIGINAL: wdolson

I haven't looked at it in some time, but I believe there is a section of the location table the editor has no access to that is used for split units.

Bill

Correct, numbers after 10000 are in game unit splits.

Agree with the OP, all of the other tables are big enough EXCEPT the location table. The IJ had only 2000 slots, the Allies 3000, that's it. Modding, you would really like to have more of both. For an AI game, you can use some more areas, but not for a PBEM as it creates some visibility issues.

But it is what it is, and it is PRETTY DARN GOOD. [;)]

[&o][&o][&o]