PvE is ahead, but this is not a technical update
Nikita Buyanov shared a breakdown of Escape from Tarkov players by mode: PvE accounts for 60%, regular PvP for 25%, and PvP Seasons for another 15%. That leaves all PvP formats at 40% combined.
It is a meaningful change for a game long associated with player-versus-player raids. Still, the figures do not prove that PvE players have abandoned PvP altogether: the source notes that some players may move between modes depending on the situation.
What it means for cheats
There is no direct cheat-status change in this report. The source does not mention a game-client update, anti-cheat adjustment, ban wave, feature block, detection, or work by cheat developers. The player split alone is not a reason to expect a mandatory update or postpone a launch.
If you are looking for software specifically for PvE, judge it by its current status, most recent update, and listed features—not by the size of the mode’s audience. Sky Cheats for EFT and SMG Radar for EFT have different feature sets, so the relevant question is which one fits your intended use.
PvE popularity does not remove risk
A larger PvE population does not change the inherent risk of third-party software. This report includes no statement from Battlestate Games about enforcement, checks, or penalties. It should not be treated as a policy change or as evidence that detection risk has changed.
Before buying or launching anything, check the current product status and its requirements. The cheat selection checklist covers the practical points to verify. Also, a lack of detection news is not proof that there is no risk: updates, detection waves, player reports, and usage patterns can all matter, as explained in Why Cheats Get Detected.
What to do now
Base the decision to launch or wait on the live status of the specific product, not on the reported PvE/PvP ratio. If its product page has no notice about maintenance or a pending update, this statistic alone does not change its status.
Do not treat PvE as consequence-free. The same preparation rules apply: review the product status, avoid mixing questionable software, and do not rely on guarantees. Review the safe launch checklist before starting a session.
Original source developer announcement