You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The configs of games with too many C++ constructors per class and per object type are too long with too many repetitive entries. What's missing is a possibility to register multiple constructors for the same class. It has been partially done with the grow handling already. The size of the object should also be included and those objects should be dumped in the biggest size.
An example for having too many constructors is the game Dune Legacy.
Even when combining only the new mission and the load mission constructor for units and structures, that would save almost half of the config lines already.
The text was updated successfully, but these errors were encountered:
The configs of games with too many C++ constructors per class and per object type are too long with too many repetitive entries. What's missing is a possibility to register multiple constructors for the same class. It has been partially done with the
grow
handling already. The size of the object should also be included and those objects should be dumped in the biggest size.An example for having too many constructors is the game Dune Legacy.
I imagine this like this:
Even when combining only the new mission and the load mission constructor for units and structures, that would save almost half of the config lines already.
The text was updated successfully, but these errors were encountered: