Extra & Tab Nodes — Galaxy Strike Online Wiki

Extra nodes and tab nodes control access to UI panels, admin tabs, and miscellaneous system features that do not fit neatly into the player/moderator/admin hierarchy.

What Are Tab Nodes?

Tab nodes gate which sections of the admin panel a player can see. Even if a player holds permission.node.admin.panel.items, they will not see the Items tab unless they also hold the corresponding tab visibility node.

Tab nodes are additive — a player only sees tabs for which they hold the node. Assigning permission.node.admin.panel.* covers all tab nodes at once.

Admin Panel Tab Nodes

Node	Description
`permission.node.tab.admin.items`	Show the Items tab in the admin panel
`permission.node.tab.admin.hostiles`	Show the Enemies tab in the admin panel
`permission.node.tab.admin.players`	Show the Players tab in the admin panel
`permission.node.tab.admin.settings`	Show the Settings tab in the admin panel
`permission.node.tab.admin.datapacks`	Show the Datapacks tab in the admin panel
`permission.node.tab.admin.reports`	Show the Reports tab in the admin panel

Extra Nodes

Extra nodes cover miscellaneous capabilities outside the main role tiers. These are typically assigned selectively to specific accounts rather than entire roles.

Node	Description
`permission.node.extra.debug`	Enable debug output and verbose logging for this player session
`permission.node.extra.bypass.cooldown`	Bypass all action cooldowns (crafting, dungeon entry, shop)
`permission.node.extra.bypass.capacity`	Bypass inventory and storage capacity limits
`permission.node.extra.spectate`	Enter spectator mode in any dungeon instance
`permission.node.extra.broadcast`	Send a broadcast message to all online players
`permission.node.extra.teleport`	Teleport to any player or location
`permission.node.extra.impersonate`	Act as another player for testing purposes (logged)

permission.node.extra.impersonate — all actions taken while impersonating another player are logged with both the operator and target account IDs. This node should only be assigned to QA and developer accounts.

Combining Tab and Action Nodes

For a staff member to actually use the admin panel effectively, they typically need both the action node and the tab node. For example, to let a Moderator view and resolve reports:

permission.node.moderator.report.view
permission.node.moderator.report.resolve
permission.node.tab.admin.reports

Complete Node List

permission.node.tab.admin.items
permission.node.tab.admin.hostiles
permission.node.tab.admin.players
permission.node.tab.admin.settings
permission.node.tab.admin.datapacks
permission.node.tab.admin.reports
permission.node.extra.debug
permission.node.extra.bypass.cooldown
permission.node.extra.bypass.capacity
permission.node.extra.spectate
permission.node.extra.broadcast
permission.node.extra.teleport
permission.node.extra.impersonate