RUNESTONE VALE

RunestoneHub

The player navigation and utility hub of RunestoneMMO — built to make important systems easier to reach without command clutter.

RunestoneHub is the Login Hub and Hub Compass module for the RunestoneMMO ecosystem. It owns the player-facing Hub menu runtime, navigation flow, Hub Compass interaction, travel menu access, market access, bank access, quest information page, server updates page, and key player utility menus.

Built on top of RunestoneCore, RunestoneHub consumes Core services instead of owning every backend itself. Core remains the authority for economy, bank data, menu framework, configuration values, quest service boundaries, travel commands, and shared player systems. Hub organizes those systems into a cleaner player experience.

In simple terms: RunestoneCore provides the foundation, while RunestoneHub gives players a central place to access the realm’s most important systems.

View on Hangar Join the Discord Back to Runestone Vale

Platform: Minecraft Java Edition • Paper 1.21.11 • Java 21
Requires: RunestoneCore
Purpose: Player Hub menu, Hub Compass interaction, utility navigation, and system access

What RunestoneHub Owns

RunestoneHub owns the Hub runtime and player navigation layer. It does not replace Core, NPCs, Skills, Combat, Stamina, or AdminTool. Instead, it gives players cleaner access to those systems through menus.

Login Hub Runtime

Owns the player Hub menu flow, page navigation, button layout, and Hub-specific menu presentation.

Hub Compass Interaction

Listens for the Hub Compass right-click behavior and opens the player Hub without forcing players to memorize commands.

Player Utility Navigation

Organizes travel, market, bank, quest, grave, mailbox, daily, skill, and update access into one connected interface.

Read-Only Quest Info

Displays current quest progress, active/ready counts, and completed quest count through the authoritative Core quest service boundary.

Newest Hub Highlights

Recent RunestoneHub work focused on making the player experience cleaner, less cluttered, and better connected to the current quest, economy, bank, and server update systems.

Quest Info Button

The main Hub now includes a dedicated Quest Info page showing current quest data, progress, active quest count, ready-to-turn-in count, and completed quest count.

Market & Bank Split

Market & Trading remains the main economy entry point, while bank actions now live in a cleaner dedicated Bank submenu.

Dedicated Bank Menu

Bank deposit and withdraw actions are grouped in their own menu with fixed amount buttons and custom amount prompts.

Server Updates Page

The Hub Server Updates page reads configured news entries and displays polished development updates in-game.

Hub Compass Polish

Hub Compass wording was cleaned up so players understand it opens the Runestone Hub for market, bank, travel, skills, and updates.

Build Validation

The latest Hub polish sequence built successfully alongside Core and NPC modules, with no extra validation edits introduced during final checks.

Module Boundary

RunestoneHub is intentionally focused on player navigation and UI. It should not become a second backend for economy, quests, NPCs, travel, skills, or server data.

RunestoneHub Owns

  • Login Hub menu runtime
  • Hub Compass right-click listener behavior
  • Hub page navigation
  • Market & Trading menu presentation
  • Bank submenu presentation
  • Quest Info read-only page
  • Server Updates/news viewer
  • Teleport Requests menu surface
  • Graves menu surface
  • Player utility menu layout
  • Hub lifecycle listener registration

Other Modules Own

  • RunestoneCore owns menu APIs, economy, bank state, commands, config values, travel commands, mail, graves, daily rewards, and quest service read boundaries.
  • RunestoneNPCs owns quest runtime, quest progress, quest lifecycle, dialogue, rewards, and NPC shops.
  • RunestoneSkills owns skill progression and skill XP sources.
  • RunestoneCombat owns combat runtime and combat XP behavior.
  • RunestoneStamina owns stamina drain, regen, HUD, buffs, and stamina items.
  • RunestoneAdminTool owns staff/admin GUI workflows.

Main Systems Inside RunestoneHub

Login Hub Main Menu

  • Main player utility menu
  • Opened by /hub, /loginhub, or Hub Compass right-click
  • Routes players to travel, market, bank, skills, quests, graves, updates, and other utility pages
  • Uses Core’s menu framework instead of a separate standalone GUI backend
  • Designed to reduce command clutter for normal players

Hub Compass

  • Player-facing Hub item
  • Right-click opens the Runestone Hub menu
  • Works through HubItemListener
  • Item authority and fallback wording are handled through the wider Core/Hub integration path
  • Polished lore explains access to market, bank, travel, skills, and updates

Travel Access

  • Spawn button
  • Home button
  • Set Home button
  • Teleport Requests submenu
  • Uses existing Core/player travel command behavior
  • Hub does not replace the actual teleport command authority

Teleport Requests Menu

  • Teleport to Player flow
  • Bring Player Here flow
  • Accept request
  • Deny request
  • Cancel outgoing request
  • Toggle receiving teleport requests
  • Menu access for players who do not want to type every teleport command

Market & Trading

  • Main economy/navigation page
  • Player Shops access
  • Auction House access
  • Trading/economy direction
  • Entry point into the dedicated Bank submenu
  • Recently cleaned up so bank actions no longer clutter the main Market page

Bank Submenu

  • Dedicated bank page under Market & Trading
  • Fixed deposit buttons
  • Fixed withdraw buttons
  • Custom amount deposit prompt
  • Custom amount withdraw prompt
  • Deposit/withdraw actions return players back to the Bank page
  • Uses Core bank/economy authority instead of storing bank state in Hub

Quest Info Page

  • Dedicated Quest Info button in the main Hub
  • Shows tracked/current quest title where available
  • Shows quest status
  • Shows objective text
  • Shows progress text
  • Shows progress percent where available
  • Shows active quest count
  • Shows ready-to-turn-in count
  • Shows completed quest count
  • Read-only display; does not mutate quest lifecycle, rewards, or progress

Server Updates Page

  • Displays configured server news/update entries
  • Reads from login_hub.news.entries
  • Supports polished in-game development updates
  • Designed for readable update summaries without external links inside the in-game entry
  • Lets the server communicate current progress from inside the Hub experience

Graves Access

  • Graves submenu access
  • Latest grave location support
  • Death recovery information surface
  • Uses Core grave systems instead of storing grave data inside Hub
  • Gives players easier access to recovery information without command spam

Mailbox & Daily Utility

  • Mailbox access/status
  • Daily Claim access
  • Streak display direction
  • Routes into Core-owned mail and daily reward systems
  • Helps recurring player utility feel connected to one Hub flow

Skills Access

  • Skills page/menu access
  • Routes players toward skill/progression information
  • Uses Core/Skills service boundaries for actual progression data
  • Helps professions feel connected to the main player experience

Fallback & Safety States

  • Clean message when player travel tools are unavailable
  • Clean unavailable state when quest provider is missing
  • Clean no-active-quest state when the player has no active quest
  • Prompts are cleared when players quit
  • Hub views avoid becoming backend mutation paths

Quest Info Contract

The Quest Info page is intentionally read-only. It exists to show players useful quest information without becoming a second quest engine.

Data Source

  • Consumes RunestoneCoreAPI.get().getQuestService()
  • Uses RunestoneQuestService snapshots and counts
  • Does not read quest config directly
  • Does not read NPC config directly
  • Does not read player quest preference storage directly

Displayed Quest Data

  • Current/tracked quest
  • Quest status
  • Objective text
  • Progress text
  • Progress percent where available
  • Active quest count
  • Ready-to-turn-in quest count
  • Completed quest count

Safety Rules

  • No quest state mutation
  • No reward claiming
  • No progress editing
  • No direct config reads
  • No NPC runtime ownership
  • Missing data resolves to a clean fallback display

How RunestoneHub Connects to RunestoneCore

RunestoneHub depends on RunestoneCore. Core provides the menu framework, command-backed player actions, economy and bank authority, configuration sources, quest service read boundary, and many of the systems displayed in the Hub.

Core Menu API

  • Hub uses Core menu creation APIs
  • Hub menu pages are rendered through the shared menu framework
  • Hub does not create a separate independent GUI framework
  • Menu readiness checks protect players from broken/opening states

Core System Commands

  • Spawn/Home/Set Home use Core command behavior
  • Teleport Requests use Core command behavior
  • Graves use Core grave command/backend behavior
  • Bank uses Core economy/bank behavior
  • Mail and daily systems remain Core-owned

Core Config Values

  • Server Updates entries are read from login_hub.news.entries
  • Hub item fallback wording is tied into the Core/Hub integration path
  • Hub consumes configured data without becoming the master config owner for unrelated systems
Explore RunestoneCore View Server Features

Commands & Permissions

RunestoneHub has a small command surface. Most of its value is in the Hub menu itself and the Hub Compass interaction.

Main Player Command

  • /hub — opens the Login Hub / Runestone Hub menu
  • /loginhub — alias for opening the Hub

Player Permission

  • runestonecore.hub.use
  • Default: true
  • Allows players to open the Hub menu
  • Used by the player-facing Hub command surface

Admin Permission

  • runestonecore.hub.admin
  • Default: OP
  • Reserved for Hub admin operations and reload/admin paths where available

Related Commands Used by Hub

  • /spawn
  • /home
  • /sethome
  • /tpa, /tpahere, /tpaccept, /tpdeny, /tpacancel, /tptoggle
  • /grave
  • /daily
  • /mail
  • /skills

Configuration & Runtime Files

RunestoneHub itself is lightweight. Much of the player-facing content it displays comes from Core configuration and Core services.

Important Runtime Classes

  • RunestoneHub — module entry point
  • HubItemListener — listens for Hub Compass interaction
  • LoginHubSupport — builds and opens Hub menus
  • HubCommandRegistrar — registers Hub command access
  • HubConstants — shared Hub constants

Config Sources Consumed

  • login_hub.news.entries — Server Updates entries
  • Core economy/bank config values where needed
  • Core quest service data for Quest Info
  • Core menu framework state
  • Core command-backed system behavior

Build / Deployment

  • Build module with ./gradlew :RunestoneHub:build
  • Deploy RunestoneHub-<version>.jar
  • Requires the matching RunestoneCore jar
  • Quest Info also depends on the active RunestoneNPCs quest service provider for real quest data

Player Experience Goals

RunestoneHub exists because a growing MMO server can quickly become overwhelming if every system requires a separate typed command. The Hub gives players one familiar place to start.

Reduce Command Clutter

  • Players can access major systems from a menu
  • Travel and teleport tools are easier to discover
  • Bank and market systems are easier to understand
  • Quest information is easier to check

Improve Onboarding

  • Hub Compass gives new players an obvious utility item
  • Server Updates help explain current progress
  • Skills, market, bank, and travel are not hidden behind command knowledge
  • Hub creates a stronger first impression for the realm

Connect Systems

  • Travel links to player movement tools
  • Market links to shops, trading, and bank access
  • Quest Info links players back to their current progression
  • Updates help connect development progress to the live player experience

Manual In-Game Test Checklist

After deploying a new Hub build, staff should test the Hub in-game as a normal player and as staff where needed.

Core Hub Tests

  • /hub opens the Hub
  • /loginhub opens the Hub
  • Hub Compass right-click opens the Hub
  • Main menu buttons appear correctly
  • Back/close navigation behaves cleanly

Menu Flow Tests

  • Market & Trading opens
  • Bank opens from Market & Trading
  • Deposit buttons work and return to Bank page
  • Withdraw buttons work and return to Bank page
  • Custom amount prompt clears properly when done or when player quits

Quest & Updates Tests

  • Quest Info opens
  • Quest Info shows clean fallback when no active quest exists
  • Quest Info shows current quest data when a quest is active
  • Completed quest count displays without errors
  • Server Updates shows the configured development update

Why RunestoneHub Matters

Runestone Vale has many systems: skills, economy, bank, travel, graves, quests, updates, mail, rewards, and more. Without a central player hub, those systems can feel scattered or hidden.

RunestoneHub makes the realm easier to use by giving players a connected utility center. It turns the server’s systems into something players can actually navigate, instead of forcing everyone to remember a growing command list.

The Hub is what helps Runestone Vale feel more like a polished MMORPG realm and less like a loose pile of separate plugin commands.

What Is Still Growing Inside RunestoneHub

RunestoneHub already provides a strong player utility layer, but it can keep growing as the rest of RunestoneMMO expands.

More Player Guidance

As quests, skills, towns, dungeons, and content worlds grow, the Hub can become a stronger place for guiding players to what matters next.

More Economy Navigation

Market, bank, player shop, auction, and trading tools can continue becoming cleaner and easier to understand.

Quest Integration Polish

Quest Info is read-only and service-backed now, but future quest systems may allow more helpful player guidance and clearer quest navigation.

Better New Player Flow

The Hub Compass can keep improving as the main commandless access point for onboarding, daily play, and player utility.

State of the Module

RunestoneHub is actively serving as the player navigation layer for Runestone Vale. It owns the Hub menu runtime and helps players access the systems that matter most during normal play.

The current direction is focused on clean navigation, readable menus, commandless utility, quest visibility, market/bank clarity, and better in-game communication through Server Updates.

This is the player utility center of RunestoneMMO — the place where the realm’s systems become easier to find, understand, and use.

Open the Hub

RunestoneHub gives players a central place to reach travel, market, bank, quests, graves, mail, daily rewards, skills, and server updates. It is one of the main player-facing pieces of the Runestone Vale experience.

Open on Hangar See RunestoneCore View Server Features Join the Discord