Advanced Loot

Use this page when you want deeper architecture, extension, and integration context for Loot.

This section is early. It will expand as the product’s implementation and public API become more concrete.

Extension Direction

Loot should support more than one level of use:

• guided configuration where Nexus is useful
• direct Blueprint workflows for common project integration
• C++ APIs and extension points for deeper customization
• project-specific adapters where the default integration is not enough

Design Boundary

Loot should stay focused on loot tables, weighted rolls, quantities, modifiers, and reward resolution.

It should not absorb unrelated gameplay ownership just because another system can trigger it, query it, or respond to it.

Integration Direction

When other Dynaros products are installed, Loot may expose richer optional integrations.

Those integrations should make combined use smoother while preserving standalone value.

Open Questions

Open questions for this product should be tracked here as implementation matures:

• which workflows belong in the default plugin
• which behaviors should remain project-owned
• which integrations should be first-party
• which APIs need stable Blueprint exposure
• which C++ extension points are required
• which diagnostics are needed for real project debugging