Palette and canvas
The ranks workspace turns the rank system into a node graph so you can drag in new items, connect them, zoom out, and immediately understand the structure of a tree.
Config EditorsA practical wiki for the RDQ editor suite, with a focus on how the ranks canvas helps you see the full progression system at a glance.
What These Editors Are For
The RDQ editor suite is designed for account-linked config editing. From the dashboard, you can open the Ranks Editor for graph-based rank editing or the Perks Editor for form-first perk editing.The biggest advantage is visibility. Instead of piecing the system together from separate YAML files, the editors visual structure, relationships, and validation can be found in one workspace before you export anything.Save your template and return later to add, edit, or update nodes. Export any changes as you refine and update your servers rank progression system.
Editors At A Glance
Graph-first
Ranks editorBest for seeing the entire progression shape at once: branches, links, dependencies, and path-level structure.Drag rank, requirement, and reward nodes from the palette onto the canvas.
Connect nodes visually instead of mentally tracing nextRanks and linked payloads across files.
Switch between path settings and global rank-system settings from the inspector.
Form-first
Perks editorBest for tightening up perk details, system rules, ordering, and nested effect configuration without hopping between many YAML files.Edit perk-system.yml in a dedicated section with focused controls and grouped YAML blocks.
Open each perk card to tune basics, icon metadata, effect settings, requirements, and unlock rewards.
Reorder perks with drag-and-drop or step controls and let the editor rewrite contiguous displayOrder values.
Why The Ranks Editor Is UsefulThis is the editor to open when you want to understand the progression system visually. It is especially strong for rank trees with branching unlocks, shared requirements, attached rewards, or several paths that need to stay coherent together.Instead of mentally resolving 
nextRanks, node payloads, and path files across the project, the canvas lets you see rank flow directly. That makes balance reviews, cleanup work, and design discussions much faster because everyone is looking at the same structure.Tree-aware editing
Each path stays grouped inside the editor, which makes it much easier to compare separate rank trees and rename, add, or remove paths without losing context.
Inspector and raw payload control
Selecting a node exposes key, label, and payload YML, while the empty-state inspector gives you tree settings and global rank-system YML in the same workspace.
Validation and export
Templates, validation, and zip export make it practical to experiment safely, catch issues early, and hand off a clean config bundle when the structure looks right.
What The Perks Editor CoversThe perks editor complements the ranks canvas by giving you a more detailed, form-driven view of perk configuration. It is better for cleaning up the actual fields that power perks than for visualizing progression shape.That makes it a good companion workflow: shape the progression visually in the ranks editor, then refine the individual perk system details in the perks editor before exporting the finished bundle.
Verification first
The perks editor surfaces missing required keys, duplicate identifiers, duplicate file names, missing effect configuration, and validation results before you export.
Focused system controls
Global perk settings stay separate from individual perks, so it is easier to adjust enabled state, limits, cooldown multipliers, and grouped YAML sections like UI or integration.
Per-perk editing
Each perk card exposes the important pieces in one place: identifier, label, file name, type, category, icon, effect settings, requirements, unlock rewards, and custom effect YAML.
Ordering tools
Review the perk sequence order and configure the in-game GUI ordering in one easy tool.
Best Use Cases
Spot branches, dead ends, or overly dense progression paths without opening every rank file by hand.
Confirm that requirements and rewards are attached to the intended rank nodes before exporting.
Compare multiple rank trees side by side and understand how the whole RDQ progression system fits together.
Standardize perk identifiers, labels, categories, file names, and ordering from one place instead of editing scattered YAML files individually.
Use templates and source snapshots to prototype safely, then validate and export when the config is ready for a server.
Suggested Workflow
Step 1
Choose your editor
Open the RDQ tool suite from /dashboard/tools and choose either the ranks or perks editor.
Step 2
Start from a source or template
Start from the active source snapshot or load one of your saved templates.
Step 3
Map progression visually
Use the ranks editor first when you want to understand or redesign progression flow visually.
Step 4
Refine perk details
Use the perks editor to refine perk-system settings, perk metadata, effects, requirements, rewards, and ordering.
Step 5
Validate and export
Run validation in the editor you changed, then export the zip bundle once the warnings and errors are where you want them.
Config Files RepresentedThese editors sit on top of the standard RDQ config layout, so what you change visually still maps back to the same core files you would edit manually.
Ranks editor
plugins/RDQ/ranks/rank-system.yml
plugins/RDQ/ranks/paths/*.yml
Perks editor
plugins/RDQ/perks/perk-system.yml
plugins/RDQ/perks/*.yml