__merge: a step to bad design

Discussion in 'Other' started by Target-san, Jun 10, 2014.

  1. Target-san

    Target-san Subatomic Cosmonaut

    Hello Starbound team.

    First of all I wanna thank you for the tremendous work you've done.

    Though I need to say that the current solution with __merge pseudo-command in tables isn't a very good solution. Because current scheme breaks mods isolation easily.

    Why I would think so:
    1. I assume that if SB has mod, it should provide maximum operation safety for each mod. This means a mod shouldn't break other mod's behavior by accident. And the current schema with "overwrite by default" effectively violates this.
    2. A mod should add new objects in a safe and easy way. Current requirement of '__merge' pseudo-field breaks this.
    3. Although mod author sometimes requires to modify existing list of objects. So we should provide some way to do so for him

    My proposal:
    1. Tables in config provide _only_ merge behavior, for safety reasons
    2. There's API called 'registry' or like which gives full power of object lists manipulation.

    Thanks.
     
  2. prodamn

    prodamn Spaceman Spiff

    this doesn't belong here! the suggestions board it where this should go!
     
    Last edited: Jun 10, 2014
  3. Target-san

    Target-san Subatomic Cosmonaut

    My apologies, I was thinking that all mod-related stuff goes to Modding forum, and that Suggestions thread is for vanilla game only.
     
  4. prodamn

    prodamn Spaceman Spiff

    it's more like,

    need help with mods ? -> modding board

    got a suggestion to everything and anything about the game ? -> suggestions

    not a big deal, a mod already moved the topic! ;)
     

Share This Page