Learn how to structure and document individual mission node pages for the Warframe Wiki. Understand schemas, data types, and required fields for accurate walkthroughs.
Hey there, Tenno! So, you're looking to dive deep into documenting those individual mission nodes on the Warframe Wiki? Awesome! Think of this as your friendly guide to making sure each mission page is super clear and helpful for everyone.
We're talking about the nitty-gritty details that make up a mission node, like its name, level range, and what kind of loot you can expect. It's all about the data!
Mission Node Entry Schema
This is like the blueprint for each mission node. It tells us what kind of information we need to include. Here’s a peek at what a typical entry looks like:
{
CreditsReward = 0,
DropTableAlias = "Drop table entry key in Module:DropTables/data",
Enemy = "Enemy faction",
InternalName = "SolNode0",
Introduced = "Vanilla",
Link = "Node article name",
MaxLevel = 11,
MinLevel = 6,
Name = "Node name",
NextNodes = { "" },
Planet = "Planet name",
PreviousNodes = { "" },
Quotes = "Quotes article name",
Tileset = "Tileset name",
Type = "Mission type",
},
Key Details Explained
Let's break down some of the most important bits you'll see in that schema:
- `Name`: This is the actual name of the mission node you see on the Star Chart, like Kappa.
- `InternalName`: The game's internal code for the node, such as SolNode0. Handy for developers and deep dives!
- `Link`: This is the name of the wiki article for that specific node. It's how players will find your detailed page!
- `MinLevel` and `MaxLevel`: These tell you the enemy level range for the node, from 6 to 11 for example. Crucial for knowing the challenge!
- `Enemy`: Which faction you'll be fighting, like Grineer.
- `Planet`: Which planet the node is located on.
- `Type`: The kind of mission it is (e.g., Survival, Defense, Exterminate).
- `Tileset`: The environment you'll be playing in.
- `CreditsReward`: The base amount of Credits you get just for completing the mission (not including pickups!).
- `DropTableAlias`: This points to where the mission's loot table is defined in the Module:DropTables/data. It's how we know what drops where!
Optional but Useful Fields
Some other fields might pop up that add extra context:
- `AdditionalCreditReward`: Extra Credits on top of the base reward.
- `Boss`: If it's an Assassination mission, the name of the boss, like General Sargas Ruk.
- `CacheDropTableAlias`: For special caches or Railjack points of interest.
- `DSResourceBonus`, `DSWeaponBonus`, `DSXPBonus`: These are specific to Dark Sectors, giving bonuses like a 0.1 (10%) Resource bonus or a 0.05 (5%) Affinity bonus for certain weapons.
- `Introduced`: The game version it was added in, like 30.5 or Specters of the Rail.
- `IsArchwing`, `IsRailjack`, `IsDarkSector`: Booleans (true/false) to mark special mission types.
- `NextNodes` and `PreviousNodes`: Shows how the node connects to others on the Star Chart, like Baal or Morax.
- `Image`: The filename for an image of the node, like Plains of Eidolon.png.
Mission Type Entry Schema
This is similar but focuses on the *type* of mission itself, like Survival or Defense. It defines things like:
- `Name`: The name of the mission type (e.g., Assassination).
- `InternalName`: Its internal code (e.g., Assassination).
- `Description`: A brief explanation of the mission objective.
- `Objective`: What you need to do to complete it.
- `Icon`: The icon used for this mission type.
Mission Modifier Entry Schema
Sometimes missions have special twists! This schema covers those modifiers:
- `Name`: The name of the modifier (e.g., Elite).
- `InternalName`: Its internal code.
- `Description`: What the modifier does.
- `Icon`: The icon for the modifier.
Data Validation
This is super important for keeping the wiki accurate. It's basically a checklist to make sure all the data is entered correctly:
- Checking for required keys: Making sure all the essential fields (like `Name`, `InternalName`, `MinLevel`, `MaxLevel`) are present for each node. If one's missing, the entry might be incomplete!
- Validating data types of values: Ensuring that the information in each field is the correct type. For example, `MinLevel` should be a number, not text. We don't want Level Six when it should be 6!
By following these guidelines, you'll be creating fantastic, detailed pages for every mission node in Warframe. Keep up the great work, and happy documenting!
100% Human-Written. AI Fact-Checked. Community Verified. Learn how AntMag verifies content