Quests and progress
Quests, story lines, badges, leaderboards, XP and level rewards.
Quests #
Quests (/manage/quests, permission quests.manage): network-wide or limited to one server group. A quest has any number of steps, each with one or more objectives (kill players, kill a mob type, break/place a block type, fish, playtime, join a group, reach a level or kill streak, complete quests, spend coins, have friends, kill bosses, sell items at or win auctions, harvest grown crops, till soil, craft, smelt, enchant or spend levels enchanting, use an anvil, brew, trade with villagers, breed, tame, milk, shear, eat, win fishing loot, clear dungeons, or a custom counter from another script; the same list as job tasks, see Jobs), and rewards (global coins, a global value, a badge, or a console command). Players start and abandon quests on the portal or in-game, see finished steps with dates, the current step's progress, and a "?" for steps not revealed yet. Up to 5 active quests; reminders on join and every 15 minutes.
More control over quests #
Everything here is on the quest form, saved in the draft like the rest and live only after Publish.
- Any N of (alternative objectives). A step's Objectives needed says how many of its objectives finish it: blank means all of them, 1 means any one ("kill the bandits or sneak past them"). Tick Optional on an objective to make it a bonus that never counts towards finishing the step; it can still send the quest down another path (below).
- Branching. An objective's Then go to step sends the quest to that step when the objective is done as its step finishes (the first such objective, top to bottom, wins). A step's Then go to does the same for the whole step: a step number, or
endto finish the quest there. Blank is the next step. Steps are numbered from the top. Going back to an earlier step starts that step fresh, so loops ("not good enough, gather again") work. A step can't go to itself, and the numbers must exist. Players see the steps they actually finished; skipped ones stay "?". The portal shows "Any 2 of these" and "(optional)". - Step rewards. Each step has its own Rewards for this step, given when it's finished (on top of the quest's rewards at the end).
- Bonus rewards. Named reward sets (e.g.
helped_breu) that the quest script gives with(Reward: helped_breu), so rewards can depend on a choice the player made. Each is given at most once per go at the quest. Names are letters, numbers,_and-. - Repeating. For a quest ticked "Can be done again after finishing": straight away, after a wait (hours), once a day (resets at midnight) or once a week (resets on Monday), and at most this many times. Players are told when they can do it again.
- Time limits. Time limit for the whole quest (minutes from starting it) and a step's Time limit (minutes from reaching that step).
/questshows the time left, and so does the portal. Running out is checked every minute (php artisan quests:expire, the task manager's "expire-quests") and whenever progress comes in. - Failing. A step fails when its time runs out, when one of its Fails if... conditions happens (any counter: "Die: 1", "Kill mobs (VILLAGER): 1", a custom script event...), or when the player leaves its place (Stay in the place: a place set with
/questplace set; leaving it after having been inside fails the step). If they fail a step: the quest fails (the default; they can start it again, it shows as "Failed" with the reason on the portal), or the step starts over (its progress and timer reset). The whole quest's time running out always fails the quest. The script'son fail { }runs either way. - Hidden (secret) quests. Not listed in
/quests, on the portal or in story lines until a player has had them, and the portal won't start them. NPC givers, starting by itself and quest scripts ((Start: slug)) still hand them out. - Tags. Comma separated (e.g.
daily, fishing, event). The quest list shows them and filters by them (Tags: at the top); in-game state carries them for other scripts. - More requirements under "Who can start it": not if they finished some quests (for "one path or the other" stories), a job they're doing now and its level, in a crew and the crew's level, badges they have, minutes played on the network, premium, a blessing they have right now, and a pet level: any pet they own at that level or higher, or pick one pet they must own (and its level).
- Quest scripts can finish the current step (
(Step: done)), move to another step ((Step: 3)), fail the quest ((Fail) "why"), start another quest ((Start: slug)) and give bonus rewards ((Reward: name)), and react withon fail { }. See Quest scripts.
Daily quests #
Daily quests (/manage/daily-quests, permission quests.manage, also a button on the quest list): every day each player gets a few quests picked at random from a pool you choose. They're ordinary quests, made and published on the quest form as usual; ticking them for the pool is what makes them daily.
- Off until you add a pool. They run while Daily quests on is ticked (the default) and at least one quest is ticked for the pool. Only live, published quests with steps are picked.
- How many a day: 3 by default (1 to 10). A player gets fewer when not enough pool quests suit them: their job and its level, and the quest's requirements (level, rank, class, earlier quests...). A quest that needs a permission can be picked on the portal and then starts the next time they join a server.
- Reset time: a new day starts at the hour you choose (midnight by default) in the panel's time zone (
APP_TIMEZONE, UTC unless set). At the reset, unfinished daily quests from the day before end as "Failed" ("The daily quests were reset"), and players online then get their new quests within a minute (php artisan quests:daily, the task manager's "daily-quests"). Everyone else gets theirs when they next join a server, open/quest dailyor open the portal's quests page. - Picking: at random, never the same quest twice on one day, and avoiding the quests a player had the day before when the pool has enough others.
- Starting: today's quests start by themselves, with one notification listing them ("Your daily quests today: ..."), and don't count towards the 5 quests a player can do at once. A player who abandons one can start it again the same day with
/quest start <name>or on the portal. - Once a day: a pool quest can only be started by a player who got it today, and only until they finish it. Its "can be done again" and story-line settings don't apply while it's in the pool. Untick it to make it an ordinary quest again; players keep the quests they already have today.
- Rewards: each quest gives its own rewards (and step rewards) when finished. The optional Bonus for finishing all of them is given once a day when a player finishes every daily quest they got that day. Players get a notification after each one ("Daily quests: 2/3 done today") and when all are done.
- In-game:
/quest daily(or/dailies,/daily) lists today's quests, their rewards, how many are done and the time until new ones. In/questsand the quest book they're tagged [Daily]. Works on 1.8 Pit and modern servers (network/Quests/Progress.sk). - Portal:
/account/questsshows "Today's daily quests" at the top, with progress, rewards and the bonus. - The page shows whether they're on, the next reset and how many players got and finished quests today. Each save is in the audit log (
quests.daily, with the settings before and after and the quests added or removed). Settings are stored as thequests.dailysetting; each player's picks are inplayer_daily_quests(App\Services\DailyQuestService).
Drafts and publishing #
Saving a quest doesn't change what players get. The form keeps your changes as a draft (everything on the form: title, steps and objectives, rewards, requirements, dialogue, auto-start, the script...), and players, servers, the portal, /quest, auto-start and story lines keep the published version until you press Publish.
- Save changes keeps the draft; Save and publish saves and publishes in one go. Saving something identical to the published version leaves no draft.
- Publish (on the quest's page, next to each quest in the list, or ticked quests with the list's Publish changes) puts the draft live: the quest and its steps are updated (steps keep their progress, matched by position as before), players doing the quest get their new state on their server straight away, and a quest script goes out with the next addons publish, within a minute. It's refused while the draft's script has errors, with the errors shown under the script. Each publish is in the audit log (
quests.publish, with what changed). - Unpublished changes: the quest's page says so at the top and lists what the draft changes (e.g. "Title, Steps, Script"); the list shows an "Unpublished changes" tag. Discard changes throws the draft away and the form shows the published version again (audit log
quests.discard). - New quests start Not published: players and servers see nothing of them until their first Publish. There's no published version to go back to, so they can't be discarded (delete them instead).
- Live / Not live is "Players can start it", a setting of the published version: tick it in the form and publish to make a quest live, untick it and publish to take it off. The list's Take off servers is the exception: it takes the ticked quests off straight away, for emergencies, and unticks "Players can start it" in their drafts too, so publishing later doesn't put them back by surprise. (There's no "Make live" action any more: going live is publishing.)
- The Story lines page sets each quest's story line, order and chapter straight away, as before; quests' drafts take the new order too, so publishing a draft doesn't undo it. Job pages likewise set a quest's job straight away.
- Under the hood, a quest's own columns and steps are the published version and the draft is kept in
quests.draft(App\Support\QuestDraft, published byApp\Services\QuestPublisher). Quests made before drafts count as published.
Quests and story lines #
Quests and story lines (story quests; staff: Quests and progress → Quests and Quests and progress → Story lines, permission quests.manage; scripts: network/Quests/QuestStory.sk and network/Quests/Progress.sk). Quests can tell a story instead of "kill 10 zombies":
- Story objectives, mixed freely with the counters above: Talk to an NPC (by name, e.g.
BreuorOld Maren, or a Citizens NPC ID), Hand in items (vanilla, e.g.BREAD, or a custom item ascitem-<ID>; taken from the player's inventory when they talk to the NPC named on it, or with/quest handinwhen it names none), and Go to a place (a spot set in-game with/questplace set <name> [radius], permissionnetwork.quests; places are listed, and can be deleted, under Story lines). There are also Kill elite mobs and Craft a custom recipe for those features to report. Any objective can have "What players read", e.g. "Bring Breu three loaves of bread". - Dialogue. A step's dialogue plays when the player talks to that step's NPC; a quest's giver has lines when it starts and when it's finished. One line each,
Name: text; a line without a name is said by the NPC, a line starting with*is narration,{player}is the player's name. - NPCs are any named mob or Citizens NPC: right-click to talk. Names match without colours, spaces or capitals. For a Citizens NPC by ID:
npc cmdadd questnpc <p> 12(runs as the console). An NPC who is a quest's giver offers the quests the player can start, with a click to accept. - Requirements to start: other quests finished first (or not finished, for branching stories), a level (the network level), a rank (any of a list), a permission (checked by the player's server, so such quests are started in-game), a class (for the classes update), a job and job level, a crew and its level, badges, minutes played, premium, a blessing and a pet level (any pet they own, or a chosen one), plus the category ("Where it counts") and job as before.
- Story lines put quests in order and in chapters; each line is the Main story or Side quests, network-wide or for one category, and shown in the order set. In an ordered line each quest unlocks when the one before it is done; with Start the next quest by itself players go straight on to the next chapter. Players see their story with
/quest story, on story pages in the/questsbook (click a quest that's ready to start it), and under "Your story" on the portal's Quests page. - Starter stories: "Add the starter stories" on the Story lines page (or
php artisan quests:starter-stories) adds, unpublished, for the categories that exist (by short name): Survival's main story The Drowned Light (8 quests in 4 chapters: a castaway, a dark lighthouse, the Drowned and their king), the side quests Tales of Saltmere (7) and The Wandering Merchant (3, in order), Pit's Rise of a Champion (5) and Pit Contracts (2, repeatable), Lobby's Welcome to Neutine (3) and Tag's Tag Academy (4, counted by Tag.sk:tag_round,tag_tag,tag_free,tag_win). Running it again only adds what's missing. Before ticking "Players can start it" and publishing them, set up their NPCs and places: Survival needs NPCs called Breu, Old Maren, Tobin, Astry, Tamsin, Mayor Oswin, Captain Rhea and Pell and the placesharbour,old_lighthouse,watchtowerandsunken_shrine; the Lobby needs an NPC called Guide. Every quest can be edited like any other. - Survival's old hand-coded quests and dialogues (
survival/game/Server/Game/QuestsandDialogues) are retired to-retired-contentfolders, which Skript skips. Their content is in the starter stories (Breu's Favour, the zombie bounty, the mining job, Astry, the welcome dialogue), NPCs that still run/neutine-worker … dialogueorquest-startare sent on to the new quests, and the survival scoreboard shows the first panel quest. - Areas and script hooks in-game: the state sent to servers carries each quest's finished steps (
done), the current step's place to stay in (area,area_name), the seconds left (time_left) and "any N of" (need).network/Quests/QuestStory.skchecks areas every 2 seconds and sendsleftwhen the player leaves one they were in; quest script hooks go to the panel as thescriptaction. - How it reaches servers: the panel sends each player's quests to their server at login, in every
/questreply, and whenever a step changes (a profile update), so NPCs and places know what's next. Talks, hand-ins and places are sent the moment they happen; items the panel doesn't need are given back, and nothing is taken if the panel can't be reached. - Starting by itself (the quest form's "Starting by itself" section). Tick "Start it for players" and choose when: when they join a server where it counts (the category from "Where it counts", or one server you pick), the first time they join the network, when they finish another quest, or when they finish a story-line chapter (every live quest of that chapter in its line). It starts once per player, only when they could start it themselves (dates, requirements, job and the 5-quest limit still apply); after abandoning it they pick it up like any other quest. A moment after each join,
network/Quests/QuestStory.skasks the panel (join), which starts what's due and replies with the giver's lines and any quest script to run; a quest that waits for another quest or chapter also starts the moment that one is finished. Players who already met the condition before it was ticked get it at their next join. Story lines' own "Start the next quest by itself" works as before. - Quest scripts (the quest form's "Script" box): a small language for what happens in-game when the quest starts, reaches a step or is finished. See Quest scripts.
Achievements and badges #
Achievements and badges (/manage/achievements, permission achievements.manage): badges with an icon, colour and requirements (the same objectives as quests, counted over a player's lifetime). Badges with no requirements are only given by staff, quests or feedback forms. Staff grant and revoke badges from the badge page or the player's Badges and quests tab. Players see earned and locked badges, with progress bars, at /account/achievements and /achievements in-game.
Leaderboards #
Leaderboards (Quests and progress → Leaderboards): rank by any stat, money or global coins, from one category or all of them, and choose the categories or servers they show on. Players see them with /leaderboard and on /leaderboards on the website. Staff with network.leaderboard put one up as a hologram with /leaderboard set <id> (and /leaderboard remove <id>).
Dungeon leaderboards (the "(Dungeons)" choices under Ranks players by, App\Services\DungeonLeaderboards): dungeons cleared, hardcore clears, fastest clear (each player's best time), fastest party clear (each party's best time, with everyone in it), raids led, dungeon mobs killed and dungeon damage dealt. They take the filters under Dungeon rankings only instead of a category: one dungeon or every one (fastest clears need one), a difficulty, the raids' schedule (daily, weekly or always open) and a period (all time, this week from Monday, or this month). Only raids that began and ended count, none from a dungeon being tested. Clears and fastest times count only players who stayed to the end: not those who left mid raid or died in hardcore. The same party (the same players) is listed once at its best time, the leader first; an equal time goes to whoever did it first. In-game, a party shows as its names ("Alice, Bob") and times as 12:05. Equal values share a rank (1, 1, 3) on every leaderboard. Results are cached for a minute; the query uses the dungeon_runs (status, ended_at) index.
XP and levels #
XP and levels (Quests and progress → XP and levels, same permission as level rewards): off by default, so each game mode keeps its own XP. Turned on for the network, a category or a server (each can use its own settings): XP needed per level is a×L² + b×L + c (default is Pit's curve) with a max level; mobs give XP per type or as hostile / passive / boss; a blacklist of mob types gives none (e.g. ENDERMAN farms), optionally also mobs from spawners; killing a player can give extra XP; and a multiplier applies to all XP, including Pit's kill XP and survival's quest XP. XP boosts are timed multipliers ("2× XP weekend") for everywhere or chosen categories/servers, stacking with the multiplier; servers announce them, and /xpboost shows what's on. /stats, /profile and the portal profile show the XP needed for the next level with this curve (or the game mode's own when the XP system is off there).
Player XP rates #
Player XP rates (Quests and progress → Player XP rates, /manage/xp-rates, permission xp.modifiers; network/Players/Blessings.sk). Change how much XP one player gets on every server, for some minutes, hours or days or until removed: for example the Curse of the administrators at 0.5× for a week instead of a ban (0 = no XP, 2 = double). The player sees the name you give it, is told when it changes, is reminded when they join while their rate is below normal, and sees it with /blessings. The reason is for staff only. It multiplies everything else: the XP settings, XP boosts and blessings, including Pit's kill XP and Survival's XP, even where the panel's XP system is off. A player's combined rate is kept between 0× and 20×. Setting and removing one is in the audit log.
Level rewards #
Level rewards (Quests and progress → Level rewards, needs levelrewards.manage): what players get when they level up, on any game mode with levels (Pit, survival). One list for the network; a category or a single server can use its own list instead. Each rule is "at level X" or "every N levels from level X", with any of global coins, a badge, a global value, a console command or in-game money (paid by the server). Each level is rewarded once per category, even if a player loses levels and gains them again; the first time a player is seen in a category they start from their current level, with no back-pay. Big jumps (e.g. a staff edit) reward at most 200 levels at once.