Skip to content

CrossSystem — Integration Samples

This folder contains optional cross-system integration samples for RevFramework.

These examples demonstrate multiple RevFramework systems working together through their public APIs.

Examples may include:

  • Economy + Inventory
  • Currency + Economy
  • Crafting + Inventory
  • Pickups + Inventory
  • Health + Status Effects

Purpose

The goal of this folder is to demonstrate:

  • real multi-system workflows
  • orchestration across services
  • adapter-driven interactions
  • public API integration patterns
  • ecosystem-level usage examples

These samples are intentionally separate from individual system folders because they depend on multiple systems simultaneously.

Structure

Integrations/
  CrossSystem/

Subfolders are typically grouped by participating systems.

Example:

CrossSystem/
  EconomyInventory/
  CurrencyEconomy/
  CraftingInventory/

SKU / Packaging Notes

Cross-system samples are intentionally separated from standalone system samples.

Why:

  • standalone SKUs should remain self-contained
  • importing a standalone SKU should never produce missing script warnings
  • cross-system scenes may depend on multiple RevFramework systems

Because of this:

  • CrossSystem content is included in RevFramework Complete
  • Some integrations may also be distributed separately as optional downloads for users who own the required SKUs

Important

These samples are:

  • optional
  • removable
  • demo-focused
  • built using public APIs only

Removing this folder will not affect core runtime systems.

Design Philosophy

Cross-system integrations should remain:

  • explicit
  • modular
  • dependency-aware
  • easy to inspect
  • easy to remove
  • isolated from core runtime code

The runtime systems themselves should remain independent wherever possible.

Third-Party Integrations

These examples are designed specifically for RevFramework systems.

If integrating with external frameworks or custom game code:

  • use these samples as architectural references
  • build your own integration layer
  • rely on documented public APIs

👉 Third-party integrations are outside the scope of these samples.

Summary

This folder answers:

“Where do multi-system RevFramework examples live?”

Answer:

Integrations/CrossSystem

These examples demonstrate how independent RevFramework systems can be combined into larger gameplay workflows while remaining modular and removable.