Treat a class perk as a specific current effect with a condition, not as a class theme. Older Amber Alert community documentation says classes had three perks and an exclusive skill, while describing skills as unreleased at that time. It also connects some classes to starting items. In 3.0, read each of those fields separately before choosing or spending Amber.
Separate four class fields
Role describes the problem a class is meant to solve, such as economy, self-reliance, utility, healing, or combat. It does not state the size of the effect.
Perk is a passive or conditional benefit. Record its exact text, activation condition, amount if shown, limit, and whether it applies to the user or team.
Starting item is equipment granted at the beginning or after a condition. Check whether it occupies inventory, needs ammunition, survives death, or depends on a Shop purchase.
Skill is an active ability if the current panel enables one. Do not assume an older “unreleased” skill became available or guess its control, cooldown, and effect.
Keeping these fields separate prevents a starting shotgun or CCTV tablet from being mislabeled as a permanent passive bonus.
Perk role checklist
Engineer as a documented example
The older community Engineer page lists a CCTV Tablet and Power Remote and describes lockdown-related perks. It also says the tablet required CCTV to be purchased from the Shop and mentioned a cooldown. This is useful because it shows how a class can depend on a map upgrade; it is not confirmation that the current 3.0 Engineer has those exact tools or values.
If Engineer appears now, inspect its panel, then load a map and confirm both inventory items. Check whether someone must buy CCTV, which feeds the tablet reaches, how it closes, and whether the remote affects the current fusebox. Record the timer from the UI rather than copying the historical cooldown.
This method turns old documentation into a test plan without presenting it as current fact.
Economy perks
Community role descriptions connect Starter, Shopper, Farmer, Jester, and Rich Kid to Shop or resource advantages. Test them against the same live item or income event. Capture the displayed price before purchase and the balance after. If the perk gives a free item, identify whether it appears at spawn, after visiting the Shop, or after a task.
Check whether the bonus is personal or shared. In a squad, one economy class may be enough if discounts or supplies benefit everyone, but that conclusion requires current observation. Do not assume multiple copies stack.
Difficulty can affect prices, and community changelogs document past scaling changes. Keep it constant when comparing.
Mobility and survival perks
For Sprinter or another movement-focused class, use the same route and starting state. Measure time only if the UI and connection are stable. More importantly, observe whether the class helps you reach a fallback without overshooting corners or creating unsafe noise.
A “resilience” description could refer to health, stamina, recovery, or another system. Use the exact current text. Do not convert a theme into a numerical claim.
Hiding-related perks should be tested only after confirming the class is available. Record the hiding surface, threat, entry and exit behavior, and whether the result repeats.
Support and combat perks
Support tests require another player and a known damage or downed state. Record range, time, charges, cooldown, self-use, and whether the mode permits revives. A faster-looking animation is not enough to publish a percentage.
Combat perks require even more control. Keep the same threat, difficulty, item, distance, and number of hits. Distinguish access to a revolver or shotgun from extra damage with that item. Record ammunition and whether the effect attracts or redirects danger.
Do not use a combat test to claim the class is best overall. The route, Shop cost, team responsibilities, and entity behavior remain part of the tradeoff.
Skills and current controls
If the 3.0 class panel shows an active skill, record the exact name and the control prompt on PC, mobile, and console. Test activation in a safe period, note cooldown or charges, and confirm whether the effect persists through death or a new night.
If the panel still says unreleased, locked, or coming later, do not create an ability description from a video or animation. A visible button can also be a placeholder until it produces a repeatable effect.
Common perk mistakes
- Copying a 2.0 value into 3.0 without reading the lobby.
- Confusing a role description with a measurable perk.
- Calling a starting item a passive effect.
- Ignoring a required Shop purchase or map surface.
- Comparing different difficulties or player counts.
- Assuming team sharing or stacking.
- Publishing a tier list after one successful run.
Source and update boundary
The perk framework and Engineer example come from the community Classes and Engineer pages checked September 5, 2026. The official Roblox experience confirms the new Shop, items, and upgrades but no class specifics. Every current perk, value, skill, item, dependency, control, and stacking rule needs the live class panel and match.
Use Classes List to choose a role and Unlock Classes before spending Amber.