NET.CRAWL Core Terms Glossary

Term Map

Use this page for NET.CRAWL glossary.

This NET.CRAWL glossary page focuses on define the recurring words that make every beginner guide easier to read. The current public baseline is app 2958140, Steam launch date Aug 3, 2026, and 1.0 context, so this page treats old demo footage as evidence only when it still matches the visible topic. The working fact set is Data, Memory, Trace, Link, Cores, Credits, callbacks, and each item has to earn its place by changing a player decision instead of decorating the paragraph. For this route, start with Data, then compare Memory against the specific board, menu, patch, support, or database question that brought the reader here. A useful player payload is: learn resource words first, then map them to node colors and route consequences on the board. That payload is intentionally narrower than a tier list because confusing Memory, Link and Trace because all three can change during one short route can mislead new players more than an honest status boundary. When the page references Steam support, achievement inventory, controller language, Depth pressure, Core behavior, Data routing, Memory timing, Trace cleanup, Link preservation, or Credits spending, it keeps the claim attached to the reviewed URLs rather than to unsourced preference. Reviewed sources: https://www.youtube.com/watch?v=da26Ek-cJ6I and https://www.youtube.com/watch?v=tD7vUw-1k0w and https://www.youtube.com/watch?v=PmKZ-OSKH9I. The added checkpoint asks players to name the exact screen, describe the visible consequence, and stop when the source does not support a stronger public recommendation. A final reading check asks whether the sentence would still help after the next board is opened; if not, keep the advice as a dated note instead of a command.

Board Language

Check Data before Memory.

Glossary Checks

Keep the conclusion limited to Data, Memory, Trace, Link, Cores, Credits, callbacks.