GG Atlas player guides
How to use game tools during a play session
A planner, map and market site can all be useful—but not at the same moment. Start with one question, use a tool to answer it, and move on when you have enough information to play.
Reviewed
A simple session workflow
Before playing, choose a goal and check its requirements. During play, keep the map or reference you actually need. Afterwards, update your progress and decide on the next achievable step. You do not need an account on every tool, and installing more software is not progress by itself.
For a more detailed decision, read the player articles and worked examples. For definitions, use the tool-type glossary.
Plan a character, team or loadout
When: Before starting a character, changing a role or spending on an equipment upgrade.
Begin with a reference that explains the idea. Write down what the setup is trying to do and which parts you can actually obtain. Move to a planner to test your own version, then check an item or skill database when a requirement is unclear. Change one assumption at a time so the comparison tells you something useful.
Which kind of tool helps?
A shared build is useful for understanding a direction; a calculator is useful for a specific comparison. You do not need both open all the time. Prefer a setup you understand over a headline result that depends on unavailable equipment.
Check before relying on it
Check the game version, platform, progression stage and calculation settings. A popular build is not automatically suitable for you, and a calculated result is not a promise about play.
A useful stopping point: Leave with one achievable next change, not an entire endgame shopping list.
Explore, find resources and finish objectives
When: When you know what you need but not where to find it or how to organise the trip.
Look up the objective or material first, then put only the relevant locations on a map. Plan the route around the places you can reach and decide whether to include optional stops. If you use a tracker, record what you actually completed rather than treating a visible marker as an unfinished task.
Which kind of tool helps?
A wiki answers why an objective matters. A map answers where it may be. A tracker remembers your progress. Start with the missing piece instead of opening three versions of the same map.
Check before relying on it
Check world, server, seed, region or scenario assumptions where they apply. Map layers can contain spoilers. Live-position and overlay features can require an installation that a browser map does not.
A useful stopping point: Leave with a short route and a clear objective. Close the extra layers.
Plan crafting, construction or production
When: Before committing materials, currency or time to a project with several inputs.
Choose the output and quantity, expand the recipe into inputs, then compare that list with what you own. Use a layout or blueprint tool if placement matters. For a production chain, test the main bottleneck before optimising every connection. For a group build, agree who provides each input.
Which kind of tool helps?
A recipe database gives requirements; a calculator estimates quantities or outcomes; a layout planner helps with space. Use the smallest combination that answers the project. Keep one working material list to avoid counting the same subcomponent twice.
Check before relying on it
Check recipe versions, server multipliers, starting stock and whether an outcome is probabilistic. A simulator does not guarantee the next craft. Save editors and imports are a separate risk: back up your own files before using them.
A useful stopping point: Leave with the missing inputs, an order of operations and a realistic first stage.
Value an item and compare a trade
When: When deciding whether to keep, buy, sell or craft a particular item.
Identify the exact item and its relevant properties in a database. Check whether you need it for progression before consulting a market tool. Compare similar offers in the appropriate market, then use a saved search or companion only if this is a task you repeat often.
Which kind of tool helps?
A database explains the item; a price-history site adds context; a marketplace shows current offers. Those are different answers. For a one-off lookup, a browser tab is often enough without an extension or desktop overlay.
Check before relying on it
Check the league, server, platform, currency and data timestamp where relevant. Asking prices are not completed sales. Review account permissions and the destination yourself before connecting a trade account or wallet.
A useful stopping point: Leave with a price range and a reason to act—or a reason to wait—not a supposedly guaranteed valuation.
Set up filters, overlays and companion apps
When: When repeated lookups or presentation problems are interrupting your sessions.
Name the interruption first: too much loot on screen, repeated price checks, or losing track of an objective. Try the browser or in-game setting before installing a tool. If an app is worthwhile, follow the project's current installation instructions, keep a backup of configuration and test one change before adding another.
Which kind of tool helps?
Filters change what is shown; overlays display information over gameplay; companions run separately. A tool can offer more than one format. Choose the format you need rather than installing the most comprehensive package.
Check before relying on it
Check the publisher's current rules, operating system, account access and disclosed behaviour. Use the project's own download source. A reachable site or a verified maintainer claim is not a malware scan, endorsement or anti-cheat guarantee.
A useful stopping point: Keep only the feature that made the session easier, and know how to disable or remove it.
Coordinate a group or operate a server
When: When a shared project needs roles, contributions, progress or server administration.
Agree on the process before choosing software: what gets recorded, who updates it and who may act. Use a shared plan or tracker for ordinary coordination. Introduce a bot or server manager only when the task requires it, and test backups and recovery before depending on the setup.
Which kind of tool helps?
A squad planner, a contribution bot and a server manager have different authority. Do not grant administration merely to share a checklist. Keep player-facing information separate from credentials and operational controls.
Check before relying on it
Check permissions, data visibility, export or backup options and what happens when the maintainer or host is unavailable. Shared records can be useful without being proof of ownership, delivery or payment.
A useful stopping point: Everyone should know where the current plan lives, who owns it and how to recover it.
Build a community tool with game data
When: When an existing tool cannot answer your question and you intend to build or contribute.
Start with the documented data interface and a small example. Confirm which endpoints or files are supported, what may be stored, and how frequently data may be requested. Build one useful read-only feature before adding account connections or automation.
Which kind of tool helps?
A static dataset, public API, SDK and modding toolkit serve different jobs. Choose the documented source closest to the feature instead of treating a website's private requests as a supported API.
Check before relying on it
Check licensing, publisher policies, authentication scopes, rate limits and update cadence. A public repository is not permission to use every service or redistribute every dataset it references.
A useful stopping point: Leave with a documented input, bounded data use and a clear way to handle an update or outage.
What GG Atlas can—and cannot—tell you
A listing brings together the source link, available formats, current recorded reachability and attributed statements. Open it before relying on an unfamiliar tool. Missing evidence stays unknown: a reachability check does not test a build, scan a download or confirm a game’s rules.