PolyLoader 2.3.1

Posts 331–344 of 344 · Page 23 of 23
i might try this, thank you.
So I'm lost on how to put in the hack file to the polyloader. I used a .zip but it says Hack file not valid. /: I'm so confused
very glad this exists, so useful. I've been using it with my own cheat for months and never been VAC'd
Does this also work on hacks for other games, I.E. Overwatch?
Quote Originally Posted by mmaaxx129 View Post
Does this also work on hacks for other games, I.E. Overwatch?
it depends on the anticheat's detection method. VAC is signature base and doesnt detect wpm but other anticheats could detect wpm etc. its safe to say this is perfect for the VAC anticheat
hack file : C:\Users\Administrator\Downloads\PolyMeme_10.3_mpg h.net.zip

compiler path : C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\cl.exe


Polyloader stopped working
...plz help me
Microsoft (R) C/C++ Optimizing Compiler Version 18.00.31101 for x86
Copyright (C) Microsoft Corporation. All rights reserved.

Decrypt.cpp
ProcMem.cpp
c:\users\aria\desktop\new folder\polymeme v3_mpgh.net_r\ProcMem.h(9) : fatal error C1083: Cannot open include file: 'TlHelp32.h': No such file or directory
Source.cpp
c:\users\aria\desktop\new folder\polymeme v3_mpgh.net_r\ProcMem.h(9) : fatal error C1083: Cannot open include file: 'TlHelp32.h': No such file or directory
Generating Code...
Press any key to continue . . .
pls help
PolyLoader 3.0 is now in a working state, at the moment I'm waiting for permission to post it as there is an installer being downloaded from Microsoft's website. (The redistributable for VC 2015, or VC 2013).



Important things to note about the new version:
It is now encouraged to use the new system for defining your files, however the old layout is still perfectly functional.

Here's an example of the new 'metadata' parser, which is the new encouraged way to define your command parameters, input, and output filenames:
Code:
// The PolyLoader version
version: 3.0
// The message displayed in File information, write a short description.
message: Hello MPGH!\nThis is just a test.
// The command line arguments given to vcvars32.bat, they can be the same as before except it is encouraged to skip the /Od flag (Debug).
command: /EHsc /MT *.cpp kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib /link /FORCE:MULTIPLE /OUT:hack.exe
// set input as the specified /OUT flag
input: hack.exe
// Set output to what you want your distributed executabl as.
output: MPGH Test.exe

// Files should now also be excluded using the exclude command.
exclude: file1.cpp
exclude: file1.h
// This does not exclude the file from compilation, only randomization.

// It is also encouraged to enter the date you released your file in, for simplicity there are 3 variables for it.
release-year: 2017
release-month: 01
release-day: 21

// And that's it for the metadata file.
The only added PolyEngine macros are [enc_string_push /] and [enc_string_pop /]. Their behaviour is defined as follows:
Code:
// at this point enc_string is disabled.
[enc_string_enable /]
// now it is enabled.

// however, if you didn't know if enc_string is currently enabled, or disabled, you might ruin the encryption for the rest of the file if, for example, you assume it is enabled.
// therefor the push/pop mechanic has been added, it is the encouraged way of using enc_string.
[enc_string_push /] // the state of enc_string [enabled] is pushed onto the stack.
[enc_string_disable /] // Now for this region encryption will be enabled.
// do shit
[enc_string_pop /] // Now we reset it back to it's original state, in this case enabled.
- - - Updated - - -
@Gaar @DarknzNet Close and Unpin this, thanks.
Alright. Closed.
Posts 331–344 of 344 · Page 23 of 23
This thread is closed for replies.

Similar Threads

Talk with us