Jaeger is an information and denial specialist. It makes hits easier to follow, warns of nearby mining, obscures sightlines, and sets traps, rewarding patient coverage of the route the objective actually needs.
A class is a battlefield responsibility, not a fixed tier. Its passive features and equipment change what your squad can safely attempt in the mineable underground environment.
What the current documentation establishes
Developer documentation and the live Roblox listing were checked on 2026-09-01. The points below distinguish documented behavior from a suggested player response. Read exact figures as a dated reference, not a promise that future servers will retain the same balance.
- Pox application. Current documentation assigns Pox per successful shot; a shotgun hit is counted per shot rather than per pellet. Treat the stated amount as balance-sensitive.
- Mining detection. Jaeger detects nearby mining within the documented radius without requiring line of sight. Use the warning to reposition or alert the squad.
- Tunnel-rat interaction. The board documents detection of Tunnel-rat users with an exception for Geist. Check current perk descriptions if this interaction changes.
- Smoke bombs. Smoke can break a hostile sightline, cover movement, or conceal a threat. State the intended direction so friendly players do not lose their own shot.
- Hunter Kit. The specialist kit provides traps. Place them where the objective and likely movement create a reason for an enemy to cross, not at random corners.
- Tracking responsibility. A mark or mining warning must become a concise call with direction, distance, and route. Silent information does not protect the team.
- Detection is not invulnerability. A warning gives time to react but does not remove explosive damage, ambushes, or an alternate opening. Maintain cover.
- Range check. The exact documented detection radius and Pox value can be rebalanced. Confirm the rule in the current class card or controlled test.
A practical way to use this information
Use this sequence when grave/digger jaeger class matters in a live round. It starts with information the interface can confirm and leaves version-sensitive experiments until they are safe.
- Confirm pox application. Current documentation assigns Pox per successful shot; a shotgun hit is counted per shot rather than per pellet. Treat the stated amount as balance-sensitive. Locate the corresponding live prompt, objective state, class description, item panel, or environment clue before committing the grave/digger jaeger class plan. Player action: State what the current server confirms about pox application.
- Connect mining detection to tunnel-rat interaction. Jaeger detects nearby mining within the documented radius without requiring line of sight. Use the warning to reposition or alert the squad. Then account for this related rule: The board documents detection of Tunnel-rat users with an exception for Geist. Check current perk descriptions if this interaction changes. The useful plan must satisfy both conditions rather than optimizing one while ignoring the other. Player action: Change one choice if the two documented conditions conflict in the current round.
- Test smoke bombs safely. Smoke can break a hostile sightline, cover movement, or conceal a threat. State the intended direction so friendly players do not lose their own shot. Reproduce that behavior with one controlled input, position, purchase, or objective action while keeping the other variables stable. Player action: Use the result to confirm or revise the working rule for smoke bombs.
- Build around hunter kit. The specialist kit provides traps. Place them where the objective and likely movement create a reason for an enemy to cross, not at random corners. Tell nearby teammates which route, resource, target, or timing this changes so their actions support the same decision. Player action: Do not assume the squad knows how hunter kit changes the plan.
- Review detection is not invulnerability and range check. A warning gives time to react but does not remove explosive damage, ambushes, or an alternate opening. Maintain cover. Compare the round result with the final caution: The exact documented detection radius and Pox value can be rebalanced. Confirm the rule in the current class card or controlled test. Preserve observations confirmed by the live server and discard the parts it contradicted. Player action: Attach changing values to the checked date instead of presenting them as permanent.
Decisions that change the plan
There is no single correct choice for every lobby. Use these decision points to adapt the documented grave/digger jaeger class rules to the round in front of you.
- Pox application or Mining detection. Current documentation assigns Pox per successful shot; a shotgun hit is counted per shot rather than per pellet. Treat the stated amount as balance-sensitive. Compare that with mining detection: Jaeger detects nearby mining within the documented radius without requiring line of sight. Use the warning to reposition or alert the squad. Prioritize the condition tied most directly to the active objective and preserve a fallback for the other.
- Tunnel-rat interaction changes the setup. The board documents detection of Tunnel-rat users with an exception for Geist. Check current perk descriptions if this interaction changes. If that condition is absent, unavailable, or already covered by a teammate, redirect the grave/digger jaeger class plan toward smoke bombs instead.
- Hunter Kit changes the timing. The specialist kit provides traps. Place them where the objective and likely movement create a reason for an enemy to cross, not at random corners. Delay the action when the squad cannot exploit the resulting opening, resource, information, or position.
- Tracking responsibility sets the limit. A mark or mining warning must become a concise call with direction, distance, and route. Silent information does not protect the team. Keep range check in view as well: The exact documented detection radius and Pox value can be rebalanced. Confirm the rule in the current class card or controlled test. This boundary is more reliable than a context-free best choice.
Common mistakes and safer corrections
Most avoidable failures come from applying a real rule in the wrong context or treating a dated number as timeless. These corrections keep the page useful without hiding uncertainty.
- Ignoring mining detection. Jaeger detects nearby mining within the documented radius without requiring line of sight. Use the warning to reposition or alert the squad. Correct the mistake by checking that condition before attempting pox application or committing a limited resource.
- Overgeneralizing smoke bombs. Smoke can break a hostile sightline, cover movement, or conceal a threat. State the intended direction so friendly players do not lose their own shot. Correct this by naming the mode, map, class, item, target, and server state in which the behavior was actually observed.
- Forgetting tracking responsibility. A mark or mining warning must become a concise call with direction, distance, and route. Silent information does not protect the team. Correct this by assigning a teammate, route, fallback, or verification check to cover the limitation before contact.
- Freezing range check in time. The exact documented detection radius and Pox value can be rebalanced. Confirm the rule in the current class card or controlled test. Correct this by comparing the checked developer card with the current interface and labelling any unconfirmed edge case as an observation.
How to verify the current server
Developer documentation and the live Roblox listing were checked on 2026-09-01. To verify Grave/Digger Jaeger Class, join through the official Roblox page and first locate evidence for pox application, smoke bombs, and range check. Compare the visible objective, menu, item description, prompt, or map geometry with the relevant developer Trello card. When they differ, preserve what the current server displays and keep the older value as dated history. If neither source confirms the edge case, change one variable in a controlled match test and label the result as an observation rather than a permanent rule.
Current-documentation note: Checked 2026-09-01. Exact balance, timers, availability, map rotation, inputs, and unlock thresholds can change. Confirm the current server UI before spending Medals or relying on a numeric breakpoint.
Continue from here
Use the related pages to turn this focused answer into a complete round plan. Each link stays inside the same source-language guide and addresses a different decision layer.
- Class index. Compare the role with the other documented squad responsibilities.
- Loadout guide. Check legal equipment, weight, and perk interactions.
- Game modes. Match the class plan to the current win condition.