NameAlreadyInUse
Regular

Othr, C++ errors and such are not directly your fault, its a game engine flaw. That's a fact and I do not want to get my post misunderstood.
But a known and most likely motive why people are having such errors even with minor battlesizes are correlated with the number of items a module has. That can be tested by playing a 400ish battle in native with no issues, and subsequently plank this (despite everything) wonderful and elaborate mod with 100 battle size with a mid/top end machine and getting the error.
I'm sure that diversity in items and such are a bliss to gaming experience, but keep this info in mind as u further development in the module.
BEST OPTION is to instead of adding entries in item_kinds, replacing existing native items with the new ones, to keep item count as close as possible to native lists, in order to minimize annoying and inconvenient runtime and RGL errors, with the frustrating knowledge that it has nothing to do with our gaming equipments.
With the best regards, othr- keep up the good work
But a known and most likely motive why people are having such errors even with minor battlesizes are correlated with the number of items a module has. That can be tested by playing a 400ish battle in native with no issues, and subsequently plank this (despite everything) wonderful and elaborate mod with 100 battle size with a mid/top end machine and getting the error.
I'm sure that diversity in items and such are a bliss to gaming experience, but keep this info in mind as u further development in the module.
BEST OPTION is to instead of adding entries in item_kinds, replacing existing native items with the new ones, to keep item count as close as possible to native lists, in order to minimize annoying and inconvenient runtime and RGL errors, with the frustrating knowledge that it has nothing to do with our gaming equipments.
With the best regards, othr- keep up the good work





