// Gameplay
Player Event States
Store persistent player and global event states for cooperating plugins.
OxideCarbon


// PRODUCT
What the plugin does
Let other plugins store a true/false value for a player or the whole server, then read it before showing or running an action. Dialogs uses these states for conditional answers and progression. Player Event States has no settings file; its integration guide explains how to use the API.
- 01Boolean states scoped to a player or the whole server
- 02Read, write and prerequisite-check APIs for other plugins
- 03Runtime-managed JSON persistence under oxide/data/PlayerEventStates
- 04An integration guide for Dialogs and custom plugins
ON PIMPMYRUST
Install the plugin
Install this version on a connected server, or download the files for manual installation.
// BEFORE YOU START
Requirements and dependencies.
- Rust server running Oxide or Carbon
- A cooperating plugin calling the documented API; Dialogs is one consumer
// IMPORTANT BOUNDARIES
Before you install
- No settings file, player command or permission to configure. A gameplay plugin uses the API to manage states.
- States are saved on server save and unload, not flushed immediately after every API call.
- Global-state reads initialize missing keys; global-state writes refuse absent keys. See the guide before integrating.
CUSTOMER REVIEWS
Plugin reviews
Your experience can help the next buyer.
No comments yet.
Write a review
Checking your account…