🎯 Building Player Profile Menus

Args (command arguments) are the secret to building parameterized menus — menus that change based on input. They power player profile menus, target-specific actions, and dynamic GUIs.

How Args Work

When a menu opens, args are everything that comes after the menu command:

/profile Notch → %arg1% = Notch

/whois Notch admin → %arg1% = Notch, %arg2% = admin

If no args are provided, NxMenu falls back to the viewer's own name as %arg1%. This makes self-targeting menus work seamlessly.

Step-by-Step: Building a /profile Menu

Step 1: Create the Menu

• FILE ID: profile_menu
• TRIGGER: profile
• DISPLAY TITLE: &8» &b%arg1%'s Profile
• ROWS: 3

Step 2: Build the Avatar Slot

Place an item at slot 13 (center):

• Material: HEAD-%arg1%
• Name: &b%arg1%
• Lore:
  &7Level: &e%arg1%:%player_level%
&7Money: &a$%arg1%:%vault_eco_balance%
&7Status: &f%isonline_%arg1%%

Step 3: Add an Open Requirement

To prevent crashes from typos in player names, set the menu's Open Requirement to:

• Type: ONLINE CHECK
• Target: %arg1%
• Deny msg: &cThat player is offline or doesn't exist!

Step 4: Deploy

Run /profile Notch in-game and watch the magic.

Passing Args to Submenus

When using the [menu] action, you can pass args by appending them after the menu ID:

• [menu] friend_actions %arg1% — Opens friend_actions menu with the same target
• [menu] confirm_purchase 500 diamond — Opens with arg1=500, arg2=diamond

The Magic Default