Ingame Commands

A complete reference of all KyuubiSoft commands, organized by mod. Includes aliases, permissions, and common workflows.

Core Commands

Command	Aliases	Permission	Description
/ksadmin	—	core.admin	Admin commands: reload configs, backup data, server info
/kscitizen	npc	core.admin	Manage NPCs: spawn, despawn, respawn, teleport, list
/ksshop	—	none	Open the shop interface
/ksdev	dev	core.admin	Developer tools: export data, get position, debug info
/kslang	—	none	Set your display language (/kslang en-US or /kslang de-DE)

Quest Commands

Command	Aliases	Permission	Description
/ksquest	questbook, qb	none	Open the quest book
/ksquestadmin	qadmin	questbook.admin	Quest admin: start, complete, reset, debug quests
/ksquestsettings	—	none	Configure quest tracker display settings

Achievement Commands

Command	Aliases	Permission	Description
/ksachievements	ac	none	Open the achievement gallery
/ksachievementadmin	acadmin	achievements.admin	Achievement admin: grant, revoke, reset achievements
/kstitles	title	none	Open the title selection screen
/ksrewards	reward, rw	none	View and claim pending rewards
/kslootbags	lb, lootbag	lootbags.admin	Manage lootbags: give, list, preview

Info Hub Commands

Command	Aliases	Permission	Description
/ksinfo	/hub, /infohub	none	Open the info hub
/ksinfoadmin	—	infohub.admin	Info hub admin: reload sections
/ksinfoitem	getinfo, infobuch	none	Get the info hub item (physical book)

Season Pass Commands

Command	Aliases	Permission	Description
/ksseasonpass	sp, seasonpass	none	Open the season pass
/ksseasonpassadmin	spadmin	seasonpass.admin	Season pass admin: grant XP, reset, manage tiers

ChatPlus Commands

Command	Aliases	Permission	Description
/kschat	chat	none	Chat settings and channel management
/kschatadmin	—	chatplus.admin	Chat admin: manage channels, mute players
/ksmail	mail	none	Send and read mail
/msg	m, tell	none	Send a private message
/r	reply	none	Reply to the last private message

Weapon Mastery Commands

Command	Aliases	Permission	Description
/ksmastery	wm, mastery	none	View your weapon mastery progress
/ksmasteryadmin	wmadmin	mastery.admin	Mastery admin: grant XP, reset, set level

---

Admin Testing Workflow

A step-by-step workflow for testing new quest content as an admin:

1. Reload Configs

/ksadmin reload

Reloads all config files from disk. Always do this after editing any JSON file.

2. Respawn NPCs

/kscitizen respawn

Forces all citizens to despawn and respawn. Required after changing citizen configs.

3. Enable Debug Mode

/ksquestadmin debugmode

Toggles the quest debug overlay. Shows:

• Current quest states for your player
• Objective progress in real time
• Trigger events as they fire
• Error messages for misconfigured quests

4. Start a Quest Manually

/ksquestadmin start <player> <questId>

Bypasses NPC interaction and prerequisites. Useful for testing specific quests directly.

5. Complete a Quest Manually

/ksquestadmin complete <player> <questId>

Force-completes a quest, granting all rewards. Use this to test reward delivery.

6. Reset a Quest

/ksquestadmin reset <player> <questId>

Resets the quest to its initial state so you can test it again from the beginning.

Full Test Cycle Example

/ksadmin reload
/kscitizen respawn
/ksquestadmin debugmode
— Walk to NPC, accept quest, complete objectives, turn in —
/ksquestadmin reset YourName my_quest_id
— Test again —
/ksquestadmin debugmode

Player Workflow

How players typically interact with KyuubiSoft mods:

Quest Flow

1. Discover — Walk up to an NPC with a quest marker above their head.
2. Accept — Read the dialog and click "Accept".
3. Progress — Complete objectives (collect items, defeat enemies, visit locations).
4. Track — Use /ksquest to open the quest book and track progress.
5. Turn in — Return to the NPC and complete the quest for rewards.

Achievements

1. Earn — Achievements unlock automatically as you play (kill enemies, craft items, explore).
2. View — Use /ksachievements to browse all achievements and your progress.
3. Claim — Some achievements grant rewards. Use /ksrewards to claim pending rewards.
4. Titles — Unlock titles through achievements. Use /kstitles to equip a title.

Info Hub

1. Open — Use /ksinfo or interact with the info hub item.
2. Browse — Read guides, server rules, and announcements.

Debug Mode

The quest debug mode (/ksquestadmin debugmode) is your most powerful testing tool. When active, it displays:

Information	Description
Quest State	Whether each quest is available, active, completed, or locked
Objectives	Real-time progress for each objective (e.g. "3/10 Oak Logs")
Triggers	Events that fire when objectives are progressed
Prerequisites	Which prerequisites are met or missing
Errors	Config errors like missing localization keys or invalid references

Debug mode only shows information to the player who activated it. Other players are not affected.

Common Issues

"Command not found"

• Check permissions — Most admin commands require specific permission nodes (e.g. core.admin, questbook.admin). Make sure your player or rank has the required permission.
• Check spelling — Commands use the ks prefix. It is /ksadmin, not /admin.
• Check aliases — You can use aliases like qadmin instead of ksquestadmin.

"NPC won't respond"

• Check citizenId — The citizenId in the quest NPC profile must exactly match the id in the citizen config.
• Check quest availability — The quest may have prerequisites that are not met.
• Reload — Run /ksadmin reload and /kscitizen respawn.

"Quest stuck in progress"

• Check objectives — Use /ksquestadmin debugmode to see which objective is not progressing.
• Check target spelling — Objective target must exactly match the item/entity ID.
• Reset — Use /ksquestadmin reset <player> <questId> to start over.

"Rewards not received"

• Check rewards config — Verify item IDs and amounts in the quest config.
• Check pending rewards — Use /ksrewards to see if rewards are pending claim.
• Check inventory space — Item rewards require inventory space.

"Config not loading"

• Validate JSON — Use a JSON validator to check for syntax errors (missing commas, unclosed brackets).
• Check server logs — The console shows detailed error messages with file paths and line numbers.
• Check file location — Custom files must be in the custom/ subfolder with the custom_ prefix.