Common Errors

Common Errors — Dog Walker Job | Quasar Store | Quasar Store

The walk timer does not move

With Config.Walk.onlyCountWhileMoving on (the default), the timer only advances while the player walks, runs or sprints — the tracker says Keep moving to advance the walk. It also stops while a dog that bolted is on the loose. Turning the option off lets the timer run regardless.

The walk ends with “<dog> returned home”

One of three things happened:

The dog was more than Config.Walk.maxDistance (100 m) from the player for three seconds in a row — usually after a teleport, or a dog told to Sit and left behind.
The timer reached zero and the additionalTime ran out before the dog was handed back.
The dog's entity was lost and could not be spawned again.

With Config.Debug on, the F8 console prints which one, with the distance and the time into the walk.

“You didn't get your money because you didn't finish the time”

The dog was handed back before its timer reached zero — that is abandoning, and it never pays.
Less real time had passed on the server than the walk's walking_time.
The server watched the player for over a minute and never saw them move — an AFK walk. This only applies while onlyCountWhileMoving is on.

“You took too long to bring the dog back”

The server gives every walk a generous real-time deadline: two and a half times the walk's length, plus additionalTime, plus ten minutes for stops and chases. A walk handed in after that is closed unpaid. It only happens when a walk is left open for a very long time.

“You have to be with the dog's owner to do that”

A walk is started and handed back in person: the player must be within 50 m of that dog's own owner at both ends. Return each dog to the owner it came from.

“This dog needs a rest before going out again”

The dog's Config.Walk.cooldown (1 minute) has not run out for this player. It starts on every ending, paid or not, and it survives a reconnect. Other players can still take that dog out.

A walk pays no money

On a standalone server there is no wallet to pay into; experience and levels are still granted. With qs-job-management running, the money goes to it rather than to the player's cash — that is intended.

[ANTI-CHEAT] lines in the server console

Printed when a client asks for something an unmodified game does not send: a walk at a location that does not exist, a walk started or handed in far from its owner, a clean-up before the dog could have stopped, or a walk finished without ever moving. Each line names the player's server id and identifier. Nothing is paid for any of them.

A single “away from the owner” line can be an honest player who walked off mid hand-over. Repeated lines from the same identifier are worth a look.

“Illegal mix of collations” in the console

The leaderboard joins qs_dog_walker to your framework's users or players table, and MySQL refuses to join columns with different collations — the default on MariaDB 11.4 and newer differs from older servers. The job lines them up by itself on every start. If it cannot, it says so and prints the exact statement to run by hand:

bash

[qs-dogwalker] could not align `qs_dog_walker`.`identifier` to utf8mb4_uca1400_ai_ci (users.identifier uses it).
  The leaderboard will fail with "Illegal mix of collations" until it matches. Run by hand:
    ALTER TABLE `qs_dog_walker` MODIFY `identifier` varchar(46) COLLATE utf8mb4_uca1400_ai_ci NOT NULL;

Run that statement in HeidiSQL or your database manager and restart the resource.

The leaderboard is empty, or the Statistics button is missing

A board only lists walkers with something on it, so a new server, a new day or a new month starts empty until the first walk is paid. Boards refresh every updateMinutes. The button itself is hidden while Config.Leaderboard.enable is false.

A winner says they were never paid

Winners who are offline at the reset have the reward banked in qs_dog_walker_rewards and paid, with a notification, the next time they load in. A row still there means they have not loaded a character since.

Key	Means
`CANT_START_WALK`	The location is not in `Config.Locations`, or the request came less than a second after the last one.
`NOT_DOG_WALKER`	The player does not hold a job in `Config.DogWalkerJob`. Checked when the walk starts and again when it is paid.
`NOT_AT_THE_OWNER`	More than 50 m from that dog's owner when starting or handing back.
`ALREADY_WALKING_THIS_DOG`	This player already has this dog out.
`LOW_PLAYER_LEVEL`	Below the dog's `required_level`.
`MAX_DOGS_REACHED`	Already walking as many dogs as `Config.LevelExperience.DogWalkingAmount` allows at this level.
`DOG_ON_COOLDOWN`	The dog's `Config.Walk.cooldown` has not run out for this player.
`DIDNT_FINISH_THE_TIME`	Handed back before the walk's time, without ever moving, or for a walk the server never opened.
`TOOK_TOO_LONG`	Handed back after the server's deadline for that walk.

Installation and Access#

Common Errors

Installation and Access#

Walks and Payments#

Leashes and Other Players' Dogs#

Leaderboard#

Message Keys#