Action Map Data Structure

Unified map node that supports four behaviors in one place: hash map, sorted map, linked map, and multi-map.

Inputs: 1 · Outputs: Then (or Yes/No for key/value checks)

Settings

Setting	Type	Required	Default	Description
Map Type	Select	Yes	Standard (Hash Map)	Select hash, sorted, linked, or multi-map behavior.
Operation	Select	Yes	Create	Choose what to do with the map.
Map Variable Name	String	Yes	—	Name of the map variable. Supports placeholders.
Scope	Select	Yes	Per Player	Where the map is stored.
Persistent	Boolean	No	true	Save map data across restarts when supported.
Sort Type (Sorted Map)	Select	No	Numeric	Sorting mode for sorted maps only.
Allow Duplicate Values (Multi-Map)	Boolean	No	false	Allow duplicate values per key in multi-map mode.
Key	String	No	—	Key used by read/write/query operations.
Value	String	No	—	Value used by set/remove-value/has-value operations.
Source Map Variable	String	No	—	Another map to merge into this map.
Store Result As	String	No	—	Variable for values, sizes, keys arrays, or counts.
Store Extracted Key As	String	No	—	Variable for operations that return a key (first/last/floor/ceiling).
Store Extracted Value As	String	No	—	Variable for operations that return a value (first/last/floor/ceiling).

Operation Notes

• Hash mode: Fast key-value lookup.
• Sorted mode: Ordered by key (supports first/last/floor/ceiling).
• Linked mode: Preserves insertion order (supports move to last).
• Multi mode: Multiple values per key (supports remove value, has value, count).

Outputs

• Most operations continue via Then.
• Has Key? and Has Value? branch to Yes and No.

Example

Store and check player metadata:

1. Set Map Type to Standard (Hash Map).
2. Use Set / Add Value with key %player_uuid% and a value.
3. Use Has Key? to branch logic when data exists.
4. Use Get Value(s) and Store Result As to reuse data later.