Post: How to make infections PRIVATE [RTM]
Options
09-05-2013, 04:25 PM
#1
JakeP0500
Do a barrel roll!
An example of the .cfg you should inject:
v ui_mapname "mp_rust; ^7This will ^1NOT ^7work for you, try if you REALLY want;bind button_back vstr exec"
v exec "exec ../../../dev_usb000/buttons_default.cfg"
How it works:
I hope this helps to make sure your infections don't get in the wrong hands!
The following user thanked JakeP0500 for this useful post:
The following 4 users groaned at JakeP0500 for this awful post:
09-05-2013, 04:53 PM
#2
Obris
Brute
Originally posted by JakeP0500
I have found a way (using You must login or register to view this content.l) to let only certain people use your infection
An example of the .cfg you should inject:
How it works:
The essential factor here is that "vstr exec". Anyone familiar with variables (or even algebra) should understand that they can equal ANYTHING. The line underneath sets that variable (the "v" is pretty much the same as "set") so the line "sets" exec (which is just the name of the variable, not the command) which is then stored on the receiving end user's Ps3, ready to be used when they activate the infection.
I hope this helps to make sure your infections don't get in the wrong hands!
An example of the .cfg you should inject:
v ui_mapname "mp_rust; ^7This will ^1NOT ^7work for you, try if you REALLY want;bind button_back vstr exec"
v exec "exec ../../../dev_usb000/buttons_default.cfg"
How it works:
I hope this helps to make sure your infections don't get in the wrong hands!
This is old. :p
The following 4 users say thank you to acceso12 for this useful post:
09-09-2013, 08:09 PM
#5
{H} | Exception
Error… Cat invasion!
Originally posted by JakeP0500
I have found a way (using You must login or register to view this content.l) to let only certain people use your infection
An example of the .cfg you should inject:
How it works:
The essential factor here is that "vstr exec". Anyone familiar with variables (or even algebra) should understand that they can equal ANYTHING. The line underneath sets that variable (the "v" is pretty much the same as "set") so the line "sets" exec (which is just the name of the variable, not the command) which is then stored on the receiving end user's Ps3, ready to be used when they activate the infection.
I hope this helps to make sure your infections don't get in the wrong hands!
An example of the .cfg you should inject:
v ui_mapname "mp_rust; ^7This will ^1NOT ^7work for you, try if you REALLY want;bind button_back vstr exec"
v exec "exec ../../../dev_usb000/buttons_default.cfg"
How it works:
I hope this helps to make sure your infections don't get in the wrong hands!
Didn't know this. Thanks for the tip ^^
The following user thanked {H} | Exception for this useful post:
Copyright © 2026, NextGenUpdate.
All Rights Reserved.
