Archaegeo / DualUniverseLuaIssues

DualUniverse LUA Issue Tracking
GNU General Public License v3.0
5 stars 0 forks source link

Additional Import Libraries #31

Closed EasternGamer closed 2 years ago

EasternGamer commented 3 years ago

Some things are better imported into Lua rather than directly placed. An excellent example is the atlas. A highly detailed list of planets. If you added it directly in your script, you would use a significant amount of your script size budget for it. Additionally, if anything changes, NQ can ensure that data is up to date.

So, as for the list, here it goes:

Example Schematic Data

{
    [sId] = { -- schematic Id
        name = "Name",
        description = "Description",
        item = itemId,
        tier = 1
    }
}

Example Item Data

{
    [sId] = { -- item Id
        name = "Name",
        description = "Description",
        schematic = schematicId,
        tier = 1,
        skills = {skillId1,skillId2,...}
    }
}

As for Atlas, something like the one found here: https://gitlab.com/JayleBreak/dualuniverse/-/blob/master/DUflightfiles/autoconf/custom/atlas_hyperion.lua

EasternGamer commented 2 years ago

Atlas and some more database/character info querying has been added! So mostly there.

NQ-Ligo commented 2 years ago

Hello !

To be honest, I wouldn't want to add more hardcoded files, like we did for the atlas if possible. For the item, we already added an item API on 0.29 Athena update to get all the information about the items from their id like a Lua table.

We will try to continue in this direction for other things ;)