[1.05b1] Decouple world map and data from scenario
Posted: Tue Aug 11, 2020 10:45 am
At the moment, world map and planet data are tightly coupled to the scenario binary serialization/deserialization.
Recommend that world map and planet data be decoupled into a predictable, separate data structure.
Structures involved with the world map and planet data should not "know about" scenario.
A decoupled, structure will allow for more options moving forward.
It will also give the scenario a predictable format, not subject to breaking changes from world building.
Yes, I understand what I am suggesting given the very brittle coupling with scenario elements like assets, etc.
This is, however, an investment in the future... like better reuse.
Device is Windows 10 Pro 64bit, version 2004 (v19041.421), Intel i7-1065G7 1.30Ghz, 16GB RAM. It is a Surface Pro 7, connected to 2560x1600 display monitor via USB-C. Intel Iris Plus integrated graphics.
For reference, Game Build v 1.05-beta1; Scenario Build 1.05-beta1; Last Game Build used 1.05-beta1; Scenario Version Number #53.
Recommend that world map and planet data be decoupled into a predictable, separate data structure.
Structures involved with the world map and planet data should not "know about" scenario.
A decoupled, structure will allow for more options moving forward.
It will also give the scenario a predictable format, not subject to breaking changes from world building.
Yes, I understand what I am suggesting given the very brittle coupling with scenario elements like assets, etc.
This is, however, an investment in the future... like better reuse.
Device is Windows 10 Pro 64bit, version 2004 (v19041.421), Intel i7-1065G7 1.30Ghz, 16GB RAM. It is a Surface Pro 7, connected to 2560x1600 display monitor via USB-C. Intel Iris Plus integrated graphics.
For reference, Game Build v 1.05-beta1; Scenario Build 1.05-beta1; Last Game Build used 1.05-beta1; Scenario Version Number #53.