#About concepts
These articles explain how the parts of a mod fit together. Read them to understand why a mod is built the way it is, before or alongside the how-tos and tutorials.
#Mods and content
About mod files and layersLearn how a mod folder is laid out, how layers group a mod's content, and how a mod replaces, patches and adds the game's files.About game content in modsLearn which kinds of content a mod can bring, which source formats it uses, and how Nebula turns them into the game's own data.
#Code
About LumaScriptLumaScript is the language for Nebula mod code. It is simple to write, it is checked against the game when you build, and it compiles to native machine code.About the game descriptionEvery build of Nebula describes itself in one file that lists every name a mod can use. LumaLink checks your mod against it.About LumaKitLumaKit is a library mod that ships with Nebula. It gives your mod ready-made parts such as new enemies, power-ups, cutscenes, HUD elements, menus and galaxies.About servicesServices are the functions Nebula gives mod code for input, saves, files, the network, audio, drawing, time and more.
#Running mods
About permissionsMods that run code ask the player before they start, and list every sensitive service they use as a permission the player can allow or refuse.How Nebula loads modsLearn what Nebula checks and prepares at each start, in which order mods load, and what happens when two mods change the same thing.When a mod failsIf a mod's code crashes while the game runs, Nebula turns that mod off and the game continues.