A SMALLER, CLEARER MAP
How the Sandboxels wiki is organized
The wiki index begins with the element because most Sandboxels questions contain a material name. From there, a visitor can move to a two-input reaction, a task-shaped guide, a controls page or a source-first mod note without losing the original context.
Recipes and guides cover decisions, while the element catalog covers nouns and properties. Controls cover interface actions, and Download covers trust and source verification. These page types are deliberately different so the site does not turn every query into the same thin article template.
The official project remains the authority for the game itself. This index adds a clearer search layer, direct internal paths and practical caveats for players who are deciding what to try next.
The Sandboxels wiki works best when you enter with a concrete question. Search an element if you need a name or property, open Recipes if you have two inputs, and choose Guides when the problem is a sequence such as making dough or finding Filter. The page you start on should reduce uncertainty and point to the next useful action, not force you to read every category first.
A wiki index also needs clear boundaries. Sandboxels can change through official releases, browser builds and community mods, so a result written for one context may not be universal. This Sandboxels wiki labels starter data, links to source pages and encourages a quick verification in the same environment where you are playing. That is more trustworthy than presenting a changing sandbox as a frozen database.
Use the element search as the central map. Once you select a material, you can move to a reaction lookup, compare it with a second input or open the recipe index for a longer explanation. The Controls page answers interface questions, while the Mods page keeps source and compatibility decisions separate. These links are designed around user decisions rather than arbitrary page categories.
The wiki is intentionally compact in its first release. Instead of creating an empty page for every possible element, it gives the most common tasks a usable tool, a crawlable explanation and a clear source note. Future entries should earn their place through real search demand, distinct behavior or a practical comparison that helps a player do something in the official game.
When you find a result that differs from the page, record the version, mod set, element names and conditions before reporting it. A careful report is more useful than a statement that the Sandboxels wiki is wrong, because it gives the next update enough context to separate a changed rule from a placement or temperature issue.
A good Sandboxels wiki should also be honest about what it does not host. This site provides a search layer, lightweight companion interactions and navigation. It does not claim to be the official game, an official download mirror or a complete mod registry. Use the official links for releases and gameplay, then return here when you need a focused reference path.
For a new question, choose the narrowest useful page. A word such as water may lead to Elements, a pair such as water and fire belongs in Recipes, and a missing button belongs in Controls. The Sandboxels wiki becomes faster to use when each page has a clear job and the internal links explain why the next page is relevant.
The index also helps readers judge confidence. Starter catalog data is a convenient reference, while live behavior in the official game is the final check. A mod source can explain why a new element exists, but it does not automatically prove that the script is compatible with every release. Keeping those roles separate makes the Sandboxels wiki easier to trust and easier to maintain.
Use the wiki search as a starting point, then follow the page that matches your decision. The Sandboxels wiki is organized to shorten that path: name and state in Elements, combinations in Recipes, interface actions in Controls, and source checks in Mods and Download.
