Skip to content
AgoraMod Launcher

Customize

Privacy, networking, and offline use

See every network category, disable egress, and prepare Agora for offline operation.

Two versions of this page follow. Step by step walks through the task in order. In depth explains the underlying behavior. They describe the same product, at different levels of detail.

Step by step

Follow the steps in order. No prior modding knowledge assumed.

Agora makes no automated telemetry calls. The Privacy section documents functional network destinations and lets Advanced-mode users disable the enforced endpoint groups individually.

After this you will be able to

  • Understand why Agora contacts each service category.
  • Use Lockdown Mode as a global network block.
  • Prepare cached data before going offline.

What network access is for

Network access can support Modrinth discovery and files, GitHub registry updates and governance, Mojang metadata and content, loader downloads, Microsoft authentication, Java runtime downloads, application updates, and optional AI services.

Use Lockdown Mode for a global block

Enable Advanced mode and open Privacy. Lockdown Mode disables every endpoint switch and blocks all outbound feature requests in the backend. Turn individual endpoints back on when you need finer control than an all-or-nothing block.

Prepare for offline play

Offline readiness is instance-specific. One prepared instance does not guarantee that another has all required artifacts.

  1. Update the Agora registry.
  2. Launch each required instance once so game and loader files are present.
  3. Confirm the selected Java runtime is installed.
  4. Download planned mods and packs before disconnecting.
  5. Disable every endpoint group and test the exact launch workflow while you still have time to correct missing files.

In depth

How the system actually behaves, and why, for readers who prefer the model to a recipe.

Build a network policy per capability and use the live status and endpoint inventory to audit Agora's functional egress.

After this you will be able to

  • Map features to endpoint permissions.
  • Apply dependency-aware network restrictions.
  • Distinguish UI consent from backend enforcement.

Apply capability-based policy

Enable only the endpoint groups needed for the workflow: registry, governance, mod discovery, launch, runtime, authentication, updates, or AI. The individual choices are the enforced policy; Lockdown Mode overrides all of them at once for a total block.

  • Disabling the Modrinth API also prevents the associated CDN workflow.
  • Runtime access is separate from Mojang game content and loader content.
  • A cached registry does not imply that every referenced artifact is cached.

Audit degraded behavior

When a feature fails, compare its service consent with its endpoint permission and the live Online/Offline indicator. Individual endpoint preferences are persisted and enforced by the Rust backend; Lockdown Mode is a global backend block that overrides them.

Protect shared diagnostics

Logs can contain local paths, usernames, server addresses, or chat context. Lockfiles intentionally omit private configuration contents, but you should still review sources and instance names before sharing. AI analysis sends selected context to its provider.

This guide is the same text Agora shows in its built-in Help & Guide, which is searchable and links directly to the screens it describes.