Learn Reputation

Use this page to understand what Reputation is responsible for before you look up exact API details.

Core Idea

Reputation focuses on faction relationships, reputation values, standing tiers, and requirement queries.

It should answer its own responsibility clearly without taking over nearby systems.

Responsibility Boundary

Reputation owns:

• reputation state
• standing tiers
• relationship values
• requirement queries
• reputation-change events

It does not own:

• dialogue writing
• quest logic
• vendor pricing implementation
• faction AI
• reward delivery

How It Fits

Reputation should be usable by itself. When other Dynaros products are installed, integrations can make workflows smoother without turning unrelated products into hidden requirements.

Working Model

Project or gameplay event
        v
Reputation plugin behavior
        v
Reputation validation / state / result
        v
Owning project or related system responds

What To Learn Next

Start with the overview if you are still deciding whether Reputation owns your problem. Use Guides for workflows, Recipes for focused examples, and Reference for exact symbols or settings.