DSK-AC

DSK-AC | Features

Anti-Wallhack / Anti-ESP

Server-side visibility system that prevents players from receiving entity data they shouldn't see. If a player is behind a wall, their data is never sent to your client, making ESP and wallhack cheats completely useless, not just hidden on screen, but removed at the network level.

Multi-Point Body Tracing

Checks visibility using up to 5 body points:

• Head
• Chest
• Feet
• Left hand
• Right hand

Includes proper crouching offsets.

Three presets control how thorough the check is:

• Fast: head only
• Medium: head + chest
• Full: all points

Automatic Distance Presets

Pairs of players close together get the Full preset. As distance increases, cheaper presets kick in automatically. Far-away pairs waste less server time on detailed checks.

Spatial Grid

Players are sorted into a 2D grid so the system only checks nearby pairs instead of comparing every player against every other player. Scales well with high player counts.

Distance-Tiered Rechecks

Hidden pairs are rechecked at different rates depending on distance:

• Close pairs get rechecked almost every tick
• Far pairs are rechecked much less often

Saves CPU without sacrificing responsiveness where it matters.

Dirty Pair Processing

When a player starts moving, all their hidden pairs are immediately rechecked, no waiting for the next scheduled recheck. Prevents players from staying invisible when the situation changes.

PVP Mode

Players who fire, take damage, or equip combat weapons enter a PVP state for a configurable duration. While active, they get:

• Stricter checks
• Longer detection range
• More pairs processed per tick
• Always the Full preset

Non-combatants are deprioritized to save resources.

Priority Weapon System

Specific weapons (like snipers) can be flagged as high-priority. Any pair involving a priority weapon:

• Gets the most thorough visibility checks
• Bypasses recheck throttling

Cannot run at the same time as PVP mode.

Position Prediction

Extrapolates where players will be based on their velocity and pre-reveals them before they come around a corner. Predicted positions are validated against world geometry so the system doesn't predict through walls.

Prop Pass-Through

Traces that hit certain props can pass through them instead of treating them as solid:

• Whitelisted models: manually listed props that should always be transparent to traces
• Translucent detection: automatically identifies props with low alpha or see-through materials (glass, fences, etc.) and traces through them

Results are cached to avoid repeated checks.

Zone System

Admins can define 3D box-shaped zones on the map:

• Whitelist zones: trace hits inside these zones are ignored, treating the area as open

• Optional validation re-traces past the zone to make sure there isn't a real wall behind it
• Blacklist zones: any trace passing through these zones is blocked, forcing players inside to stay hidden regardless of geometry

Zones are saved per-map and persist across server restarts.

Zone Creator Tool

An in-game weapon for admins to place and remove zones:

• Left click: sets the first corner
• Right click: sets the second corner (zone is created)
• R: remove the nearest zone
• E: toggle between whitelist and blacklist mode

Existing zones are drawn as colored wireframes:

• Cyan: whitelist
• Red: blacklist

Idle Detection

Players who haven't moved for a configurable time are marked idle. Idle players are deprioritized to avoid wasting traces on stationary pairs. As soon as a player moves, they are immediately reprocessed.

Player Whitelist API

Other addons or server operators can call:

DSKAC.Modules.AntiESP.Whitelist(ply, true)

This exempts a player from the system entirely. That player will always see everyone and never be hidden.

Killswitch

Console command:

dskacantiesptoggle

Instantly enables or disables the entire system from the server console. When disabled, all hidden pairs are immediately revealed.

Hot-Reload Config

Configuration changes are tracked with a version counter. The system detects changes each tick and rebuilds all internal lookups automatically, no server restart needed.

Clean Lifecycle Handling

Player spawns, disconnects, and weapon switches are all handled:

• Hidden pairs are cleaned up on spawn and disconnect
• Weapon changes invalidate caches and trigger rechecks where needed

DSK-AC | Performance

This system was built from the ground up to handle 128-player servers without dropping frames. Every part of it, from how players are tracked to how traces are fired, was designed around one question: how do we do less work per tick without cutting corners on accuracy.

No unnecessary work

The system only checks player pairs that actually matter.

• A spatial grid sorts players into cells so the server never wastes time comparing two players on opposite ends of the map.
• If neither player in a pair has a PVP weapon out and PVP mode is active, the pair is skipped entirely.
• If both players are standing still, they are removed from processing altogether.
• Every check has an early exit.

Batched processing

Player pairs are not all checked in one tick.

• The workload is split across ticks using cursor-based pagination.
• A fixed number of pairs are processed per tick, then the cursor advances.
• Hidden pairs are rechecked the same way.

This keeps the per-tick cost flat and predictable, regardless of player count.

Distance-aware scheduling

Not all pairs need the same attention.

• Close pairs are rechecked almost every tick.
• Medium-range pairs are rechecked less often.
• Far pairs are rechecked rarely.

The system also scales trace detail by distance:

• Close players get a full 5-point body check
• Far players only get a quick head trace

Result: most of the server effort goes where it matters most.

Instant response where it counts

When a player starts moving, all their hidden pairs are immediately rechecked that same tick, no waiting for the next scheduled pass.

• Done through a dirty-flag system with a reverse index, so finding affected pairs is instant.
• Players coming around corners or peeking an angle are never stuck invisible.

Zero garbage collection pressure

Everything used in the hot loop is pre-allocated once and reused.

• Trace structures, filter tables, and vectors are reused forever.
• Pair keys are integers built with bit-shifting, not string concatenation.
• The pair queue is a flat array stepped through with arithmetic, no per-pair table creation.
• Caches are cleared by overwriting fields, not creating new tables.

This produces effectively zero garbage for Lua’s collector during gameplay.

Smart caching

Expensive results are cached and only recalculated when something changes:

• Player positions cached once per tick so nothing calls GetPos twice on the same player.
• Child entities (weapons, attachments) cached and only invalidated on weapon switch or entity spawn.
• Translucent prop detection cached for several seconds with a lazy sweep.
• Predicted positions cached per-tick per-player so duplicate prediction requests are free.
• Config changes tracked with a version counter so internal lookups rebuild only when needed.

Bounded worst cases

Every loop that could spiral has a hard cap.

• Prop pass-through is limited to a fixed number of re-traces.
• Zone validation has a maximum retrace depth.
• Distance tier recalculation is throttled so it doesn’t run every visit.
• The tick counter resets before hitting precision limits.

Nothing in the system can run away.

PVP mode as a performance tool

PVP mode is not just a feature, it is a performance strategy.

On a 128-player server, most players are not fighting at any given time. PVP mode focuses the system’s budget on combatants by giving them higher throughput and longer range, while non-combatants are filtered out of the queue entirely.

The server spends its resources on the players shooting, not the players standing around.

Configurable throughput

Every performance knob is exposed in the config:

• Pairs per tick
• Hidden rechecks per tick
• Recheck intervals
• Idle timeout
• Batch sizes

Defaults are conservative and safe for most servers, but with a tuned 128-player setup (PVP mode enabled and sensible preset distances), the system stays well under budget.

The right config for your server is the difference between running comfortably and running hot.