[Release] Rust Radar topic

Hey There.

I'm a new poster to this site, but not new to the scene. I've been writing hacks since around 2007, and this is my contribution to one of the finer sites around. I'm a fan of more subtle hacks, so this won't make you leet, but it might help you make good tactical decisions.





Features

• Player radar, with names.


• Overlay mode, if you play windowed.


• Show airdrop paths and supply crates.


• Sound alerts for the things above.


• Passive, packet based system, no file modifications.

Usage:

Just run before you connect to a server. You can run it afterwards, but it won't display all the names. The file will rename itself randomly the first time it's run. It also checks and alerts you if the version has been marked as detected.

• Red dots: Active players.


• Pink dots: Last known position of a player, times out after a short period.


• Green dot: Friendly player, right-click to set someone friendly.


• Overlay: Right-click and choose Minimal.

Requirements

WinPcap
http://www.winpcap.org/install/default.htm

Visual C++ Redistributable for Visual Studio 2012
http://www.microsoft.com/en-us/downl....aspx?id=30679

Microsoft .NET Framework 4.5
http://www.microsoft.com/en-us/downl....aspx?id=30653


DOWNLOAD
(Pending approval)

Place to test RPM radar topic

Hello folks,
With all the help available here, I started writing my own DayZ Mod radar. Within about 2 hours of starting to write one, I got a GB from BE (again, this was on the mod). I learned instead to find "No-CD" but BE enabled servers where I could test my external radar without the risk of losing a key. When I was all happy with the program to use, I would run it through an external obfuscator and it would go undetected.

Anyone have any similar methods for testing a program for SA? It doesn't even have to be live. I wish there was some way to take a "screen capture" of the memory at a certain point and then just build my SA radar up from there.

My understanding that it is not so much the reading from memory that BE detects but it was how one goes about getting the process handle. At least that is how Chicken explained it to me. I understand the whole RPM process, just not how BE/VAC goes about detecting it.

Humbly,
Gecko