Converge rmgen1 and rmgen2
|Reported by:||elexis||Owned by:|
|Priority:||Nice to Have||Milestone:||Backlog|
Follow up to comment:3:ticket:4804.
rmgen2 should probably have the globals removed, especially
g_TileClasses and each map should specify the used tileclasses, even if there are some very common definitions IMO. This way the library functions don't have any state but their output solely depends on the passed arguments, making it easier to understand their results (for instance which properties of
g_TileClasses are unused by a map).
rmgen2 becomes a bit more similar to
rmgen2 functions, especially
addElements could be used by
rmgen/wall_builder.js might form a new library (Layer 3 in the ticket comment), whereas the remaining
rmgen prototypes (Painters, Placers, Constraint, Map, ...) would become the Layer 2 of the rmgen stack.
This way mods can create random map scripts that reuse reuse the basic map creation tools without importing a dictionary of ancient history rts terms.