Documentation
/guitarcreator Says I Have No PermissionCause: the ACE permission is not granted.Solution: add this to your server.cfg and restart:add_ace group.admin command.g
Cause: the ACE permission is not granted.
Solution: add this to your server.cfg and restart:
add_ace group.admin command.guitarcreator allowThe same permission covers /guitarmusic and /guitarprogress.
Cause: guitarpro-assets is , or it starts the main resource.
Solution: ensure the assets first:
ensure guitarpro-assets
ensure qs-guitarproThis is also what causes the creator to report that a model could not be loaded.
Cause: the SQL file was never imported, so the shipped charts are not in the database.
Solution: import database/sql.sql once and the 18 songs are ready immediately.
Cause: the resource has not been restarted since the file was added.
Solution: restart the resource. Files are served through the manifest, so a new one is not visible until then.
If it still won't detect, check the name — only letters, numbers, _ and - are servable. Anything else is renamed automatically when the resource next stops.
Cause: the track has no steady percussion to lock onto.
Solution: the overlay says which step failed. "No clear beat was found" and "the tempo could not be tracked" mean the same thing in practice.
Ambient, rubato and heavily live material will not chart well. Set the BPM by hand in the music manager and regenerate.
Cause: either the video cannot be embedded, or the drift never comes down.
Solution: an un-embeddable video cannot be fixed from here — use a different upload. Otherwise tap for longer before judging it, and if you know the real BPM, type it instead of tapping.
Cause: audio latency.
Solution: adjust Config.Gameplay.audioOffsetMs. It ships at -90; more negative pulls the timing earlier.
This is per-server, not per-player.
Cause: the note density or the hit windows don't suit your players.
Solution: Config.Beatmap.difficulties sets the density, Config.Gameplay.judgments sets how forgiving the windows are.
Changing the density only affects charts generated after the change. Regenerate the songs you want re-cut.
Cause: the rock meter is too punishing.
Solution: soften Config.Gameplay.life — raise start, lessen miss and bad — or set failEnabled = false to turn failing off entirely.
Cause: the machine has one pad, or those modes were not ticked for it in the creator.
Solution: both modes need a 2-pad machine. Edit the machine in the creator, or place a new one with two pads.
Cause: the shot list was framed for a different venue.
Solution: every shot is an offset from the performer, so a new venue needs no camera work by default. If you want different framing, run /guitarcam and print a new shot list.
The crowd is per-venue and does need placing — use /guitarcrowd.
Cause: the prop has not been tuned.
Solution: run /guitarplace <machine|stage> <guitarId>. The shipped guitars are already done; base-game props generally are not.
Cause: the video was made private or deleted.
Solution: these songs stream from YouTube on each player's client, so they depend on the video staying up. Add a different upload, or use a file in songs/ instead — those have neither problem.
Cause: they are gated behind Config.Debug.enabled.
Solution: set it to true while setting up — and back to false before going live.
Cause: development traces around the music manager's save and delete calls.
Solution: they are noisy but harmless. Nothing is wrong.