Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
as they need to prepare every for of requirements that players may want to apply as goals.
EDIT: i see, most huge work is done by now...
After that framework is set, the strings used would need to be defined and localized. All "season missions" AKA expedition milestones are defined in SEASONALMISSIONTABLE.EXML, and the localizations of the current expedition descriptions are stored in the 8th localization tables (NMS_LOC8_<Language>.EXML). Then, any NEW rewards, such as expedition-themed posters, would need to be defined in the building part and reward unlock EXMLs and localized.
The big problem here data retention. The reason we keep unique expedition rewards is because those reward definitions have been permanently added to the core game data, specifically in UNLOCKABLESEASONREWARDS.EXML. Once you complete an expedition, that save also retains a record of the completion and its milestone badges. If one swapped out one modded expedition for another, the previous save would break if it was kept, unless only "vanilla" assets were used for badges, patches, and rewards. Any expedition phase rewards assigned to the account would be lost upon swapping out the modded expedition unless newer modded expedition definitions were constantly merged into an ongoing mod file, as the definitions that say "^COOLMODEXPSHIP" is available for redemption would be gone. Said merged mod would then need to be updated every time the game is updated, and players would have to learn how to update it themselves for their personal set of custom expeditions run or else potentially lose everything if they accidentally save once while the merged mod remains out of date.
So, while we are completely in a position to make custom expeditions, there are limitations based on how mods and saves interact that make them unfeasible or at least unrewarding to anybody but those that just want to play the modded expedition unless the modder only used assets and rewards that already exist in the game. Maybe one day, when someone creates a better mod management system than AMUMSS or if HG stops updating NMS and decides to openly support modding, but for today it's just not feasible.
Edit: In a good mood today. The weather is finally cooperating and letting me get some yard work done, and my cat hasn't bitten me yet.
Just to be clear, I'm all for custom expeditions. I'm on the side that believes users should be able to mod games however they want as long as it doesn't directly impact the fun of others and that the Micro Star v. FormGen[en.wikipedia.org] ruling was a mistake. I just wanted to highlight the fact that there are some currently inescapable hurdles preventing such a concept from being fun.