paul01784/meatyeftrelease

Purpose and Build Entry

MeatyEFTRelease is a Windows C++ companion/radar for Escape from Tarkov. It runs outside the game process, reads game state through DMA/VMM facilities, and presents live radar and helper data. Build/open entry is MeatyEFTRelease.slnx; executable startup is expected in MeatyEFTRelease/main.cpp, with the Visual Studio project at MeatyEFTRelease/MeatyEFTRelease.vcxproj.

Application Orchestration

The top-level runtime coordinates configuration, global state, background work, and rendering. MeatyEFTRelease/main.cpp is the process entry point; MeatyEFTRelease/globals.cpp and MeatyEFTRelease/app/globals.h provide shared application state. MeatyEFTRelease/taskManager.cpp and MeatyEFTRelease/app/taskManager.h indicate a task-based control boundary for recurring work such as game-state updates and external queries.

Memory and Input Boundary

The memory layer isolates low-level interaction with the target environment and hardware/software DMA stack. MeatyEFTRelease/memory/Memory.cpp and MeatyEFTRelease/memory/Memory.h are the primary access abstraction; MeatyEFTRelease/memory/Registry.cpp and MeatyEFTRelease/memory/InputManager.cpp support environment discovery and input handling. Runtime dependencies include MemProcFS/VMM and LeechCore binaries/libraries represented by MeatyEFTRelease/libs/vmm.lib, MeatyEFTRelease/libs/leechcore.lib, and associated headers.

Game-State Extraction and Domain Model

Game modules translate raw memory into Tarkov-specific entities and world state. MeatyEFTRelease/game/maingame.cpp and MeatyEFTRelease/game/game_world.cpp appear to establish the active game/world context. Entity readers cover players, loot, camera, extracts, explosives, quests, and dogtags, including MeatyEFTRelease/game/players.cpp, MeatyEFTRelease/game/loot.cpp, and MeatyEFTRelease/game/questManager.cpp. Unity-facing types/helpers form the key boundary between raw reads and domain objects: MeatyEFTRelease/game/headers/unitysdk.h and MeatyEFTRelease/game/headers/sdk.h.

Radar Rendering and UI

The presentation pipeline converts extracted game state into an interactive DirectX9/ImGui view. Rendering is centered on MeatyEFTRelease/render.cpp, MeatyEFTRelease/app/render.h, and MeatyEFTRelease/app/draw.h; map data is managed through MeatyEFTRelease/maps.cpp and MeatyEFTRelease/app/maps.h. The desktop/window boundary is MeatyEFTRelease/DxRenderWindow.cpp with MeatyEFTRelease/app/DxRenderWindow.h. ImGui’s Win32/DX9 backends are vendored in MeatyEFTRelease/external/imgui/backends/imgui_impl_win32.cpp and MeatyEFTRelease/external/imgui/backends/imgui_impl_dx9.cpp.

Live Data, Persistence, and Updates

Network-backed enrichment is separated from local game reads. MeatyEFTRelease/game/tarkovdevquery.cpp suggests Tarkov.dev data retrieval, while MeatyEFTRelease/DogTagAPI.cpp handles dogtag-related API integration. MeatyEFTRelease/FileUpdater.cpp provides update/download behavior. libcurl is supplied through MeatyEFTRelease/external/curl/curl.h and MeatyEFTRelease/libs/libcurl.lib; JSON parsing/configuration uses MeatyEFTRelease/external/nlohmann/json.hpp, MeatyEFTRelease/config.cpp, and MeatyEFTRelease/configs/config.json. Proprietary authentication, APIs, and backend databases are explicitly outside this repository.

Supporting Runtime Options

An optional Fuser rendering/application path exists in MeatyEFTRelease/fuserapp.cpp and MeatyEFTRelease/app/fuserRender.h. Configuration and INI-based runtime settings are represented by MeatyEFTRelease/app/config.h and MeatyEFTRelease/INImeatyEFT.ini. The principal platform stack is Windows, Visual Studio/MSVC, DirectX9, ImGui, GLM (MeatyEFTRelease/external/glm/glm.hpp), and nlohmann JSON.