Certified playtester program

Known issues

This is the known-issues list used for completed Cohort 4. It remains available as part of that cohort's record and does not define a future cohort.

Cohort 4 archived paid scope · wave-4-ctf-range-core-v1

CTF to Range core loop

Paid findings were limited to CTF, The Range, Core-loop support. You may explore anywhere. Record observations outside this scope in the separate out-of-scope notes field; we will read them, but they are not paid findings and do not block this wave's core-loop decision.

Read the complete scope in the playtester terms and rubric.

Cohort 4 · updated August 5, 2026

  1. Known issue 01in-game-bugreport-prefix

    In-game bug reports require the command prefix

    While a game is active, use “:bugreport”; bare “bugreport” is routed to the game. The guided form explains the prefix outside a game, but it remains easy to miss in play.

  2. Known issue 02ctf-panel-hardcoded-line-breaks

    CTF instructions wrap prematurely in the right-hand panel

    Author-supplied newlines in instructional text force short lines before the panel’s available width, making the briefing harder to scan.

  3. Known issue 03terminal-mobile-output-wrapping

    Some terminal and crawler output does not reflow or follow correctly on mobile

    CTF post-flag explanations and some crawler output can remain wider than the viewport or be cut off, and newly wrapped description lines do not always scroll into view.

  4. Known issue 04ctf-files-perms-missing-sudoers-directory

    Permission Audit points to a missing sudoers directory

    The audit checklist tells the player to review /etc/sudoers.d/, but that directory is not present in the scenario filesystem.

  5. Known issue 05ctf-hints-ignore-completed-objectives

    CTF hints do not follow the unfinished objectives

    The hint counter advances through walkthrough steps in a fixed order without considering which objectives are already complete. A hint can therefore describe earlier work, appear out of order for what remains, or run out while an objective is unanswered.

  6. Known issue 06ctf-module-autocomplete-display-name-collision

    CTF module autocomplete duplicates Files & Permissions

    At module selection, typing “files” can surface both the executable “files-perms” module ID and its “files & permissions” display name, making the completion compete with itself.

  7. Known issue 07ctf-repeated-objective-locations

    Several CTF levels reuse the same objective locations

    A sequence of CTF levels can place flags or objective evidence in the same locations with little variation, so repetition tests recall of the path more than transfer of the underlying skill.

  8. Known issue 08ctf-step-objective-counts-differ

    CTF investigation steps and objectives are not one-to-one

    One guided investigation step can reveal evidence for multiple objectives, but the current outline does not explain that relationship. A scenario can therefore show fewer steps than objectives without saying why.

This page is the shareable archive. The same list is frozen into every submitted cohort report for later review.

Interested in a future cohort?

Cohort 4 submissions are closed. A new application joins the candidate pool only; any future cohort will publish its own known-issues list and require a separate offer and acceptance. Review the program terms and cohort archive.