New Idling Method - In-game idling made reliable - Games

[b]Note - If you think in-game idling is risky, then why are you here? This script is meant for people who currently idle in-game already.[/b] You might remember this old thread of a broken guide that never got the chance to be fine tuned by the author before it was deleted. [url]http://www.facepunch.com/showthread.php?t=805043[/url] The author went to sourceop to continue his work and now it is completed and made extremely extremely quick and simple to setup. [url]http://www.sourceop.com/modules.php?name=Forums&file=viewtopic&t=2086[/url] - 2 video modes, 1 to idle, 1 to play - Autoreconnect if you get disconnected - Autoconnect at TF2 idle mode launch - Cycles through a list of servers you add to a text file Just read the damn post ;) It's already explained in the post, but I iterate : It only a batch script for cmd.exe [windows command console] so the only thing running is cmd.exe and the unmodified TF2 client. Hence, no way in hell it is VAC bannable and no way in hell they can see you're using the script to launch TF2 since it's only CMD.exe!!!!

Isn't this what got people weapons taken away? :rolleye:

Hats, too. Valve's gonna crack down on this one just as they did with the old idler.

Guys, read the post. It's not a program It's a script that launches the normal TF2 client and connects you to a normal achievement_idle server of your choice. It's a batch script To Valve, using this script to launch TF2 is identical to launching TF2 manually. It's the same client,same everything. There's no emulating of netcode, there's no 1 big server, there's no tracking of players. It IS in-game idling, with cmd.exe running in the background to write into a config file [like autoexec.cfg] a console command that is either "retry" or "connect to xx.xxx.xxx.xxx:27015" whenever you get disconnected. TF2 reloads that .cfg file because there's a looping alias using the "wait" command in TF2. So when the script writes into the .cfg file, and TF2 reload that CFG file, TF2 executes the commands in it. THen the script deletes the content of the cfg file so that TF2 doesnt reconnect over and over and over. Basically, it automates tasks you can do manually without touching the TF2 client. TF2 client does its own thing. cmon,read the post, you'll understand. If you fail to understand the difference between "batch script + tf2 client" and the steamstats program,then it's your loss. Enjoy logging into a server before bed, then getting disconnected 30 minutes later.

And have you ever thought that Valve would figure this out, or even that they've probably got people on FP, who're right now looking at this topic and shaking their heads with disdain?

Fuck I don't care if it's proven safe, I'm not using it because I'm just not lucky like that.

[QUOTE=BeefMcGraw;17828184]Guys, read the post. It's going to remove all your items when VALVe finds out. It's going to remove all your items when VALVe finds out.It's going to remove all your items when VALVe finds out. It's going to remove all your items when VALVe finds out. It's going to remove all your items when VALVe finds out.It's going to remove all your items when VALVe finds out.It's going to remove all your items when VALVe finds out.It's going to remove all your items when VALVe finds out. It's going to remove all your items when VALVe finds out.It's going to remove all your items when VALVe finds out.It's going to remove all your items when VALVe finds out.It's going to remove all your items when VALVe finds out. It's going to remove all your items when VALVe finds out.It's going to remove all your items when VALVe finds out. It's going to remove all your items when VALVe finds out.It's going to remove all your items when VALVe finds out. It's going to remove all your items when VALVe finds out.It's going to remove all your items when VALVe finds out. Basically, it automates tasks you can do manually without touching the TF2 client. Which will get all your items removed when VALVe finds out. It's going to remove all your items when VALVe finds out. It's going to remove all your items when VALVe finds out.It's going to remove all your items when VALVe finds out.It's going to remove all your items when VALVe finds out.It's going to remove all your items when VALVe finds out.[/QUOTE] Yeah, that's pretty much what I thought, thanks for clearing that up. [highlight](User was banned for this post ("why reply" - Spork-Juct))[/highlight]

[QUOTE=Smirnoff Joe;17828205]And have you ever thought that Valve would figure this out, or even that they've probably got people on FP, who're right now looking at this topic and shaking their heads with disdain?[/QUOTE] Im sure valve is aware of the script. The point is, there's no way they can detect that the script is being used. It does not touch TF2 other than through user editable config files [autoexec.cfg, config.cfg etc, any user made .cfg] The only way it knows you have been disconnected is because TF2 dumps the content of the console in a .TXT file [text file]. Just type "con_logfile status.txt" and TF2 will dump all the console text into "status.txt" in your TF folder. Tell me, how would Valve detect that cmd.exe is being run? and why would they punish people for having cmd.exe running? heck the only way they found the steamstats users is because it connected to one server. They traced that server IP back to the users. This script uses ANY achievement_idle server. I could be idling right now in the same server as you.

It's legit. As long as TF2 actually runs, and you're on a proper server, it's fine. And it won't VAC you since it doesn't fuck around with the dlls. [editline]06:43PM[/editline] They wouldn't do anything even if they detect that cmd.exe runs, since it's only used to do some minor things.

Well, you've got them there. But this ain't over. They're capable of adapting to whatever threat they face, and this may be no exception.

[QUOTE=Smirnoff Joe;17828297]Well, you've got them there. But this ain't over. They're capable of adapting to whatever threat they face, and this may be no exception.[/QUOTE] The only threat to using this script is if Valve goes after ALL AND EVERY achievement_idle players, no matter if you're using the script or not. If you're a believer than Valve will go after in-game idling,then obviously this script is no different., If you believe that in-game idling will always be safe, then this script is for you.

[QUOTE=Smirnoff Joe;17828297]Well, you've got them there. But this ain't over. They're capable of adapting to whatever threat they face, and this may be no exception.[/QUOTE] You're not running an external program to simulate being in TF2, you're actually in TF2.

Well, if it's as simple as that, just staying in an idling server, then we're boned. Either that, or it'll encourage Valve to work on the Crafting/Trading System faster, which'll end up with it being a bit rushed. Hope you're proud of yourself, Beef. *contempt*

[QUOTE=Smirnoff Joe;17828386]Well, if it's as simple as that, just staying in an idling server, then we're boned. Either that, or it'll encourage Valve to work on the Crafting/Trading System faster, which'll end up with it being a bit rushed. Hope you're proud of yourself, Beef.[/QUOTE] This script won't magically get 10000 people to idle. Steamstats was a whole other ball game. It broke the EULA by emulating netcode, it was a modified TF2 client. It is still going to require you to run TF2, and run it on a computer that CAN run it [ I used to run steamstats on my crap laptop ]. And if you're afraid, you can always use the script to idle on a huge list of foreign servers that play legitimate map. You'll probably get banned from a few for constantly coming back every time you get autokicked, but they're foreign servers ;) Best case scenario of this script, Valve fixes the drop system. Worst case scenario of this script, Valve somehow makes idling not get any drops.

It seems perfect...but I just don't know what to trust any more.

[QUOTE=OutOfExile;17828522]It seems perfect...but I just don't know what to trust any more.[/QUOTE] You can read every file of the script in notepad and see it's all pure Windows commands. Might be complicated to understand even if you know your batch scripting, but believe me, it's all CMD.exe scripting that makes it invisible to Valve to see you're using this tool to add to your in-game idling. As I said before, the only way that Valve can punish you for using this script is that Valve punishes all in-game idlers, script or no scrip.

It seems perfect, but Drunken f00l's program seemed to me perfect, too. I'm not risking anything, I'll just wait for that crafting thing and hope it'll lead me to my favorite hat. And I read everything, but I just don't want to risk Valve finding out.

I've given up on idling after my first hat that I got by "Not cheating". From what I read, It seems fine. But I think people will choose "the moral highroad" and just join an idle server normally.

It's same bat file that you can use to create dedicated servers by one click etc. I am not gonna bother with this since I don't give a crap about hats anymore.

[QUOTE=BeefMcGraw;17828450]Best case scenario of this script, Valve fixes the drop system. [/QUOTE] there's nothing wrong with the drop system items such as hats are meant to be rare, it isn't meant to be easy to acquire them you're supposed to play the game to get them

No Thanks, I Don't like my luck

You don't exactly have to be 'playing' TF2, just running it. There is nothing stopping you form getting an item while just standing there. It doesn't detect that you're moving to give an item, then you can just get on one of the old Scout Achievement Servers and stay in the run lane and get 23 items overnight.

Knowing me, "96%" of the TF2 community will get another gay freebie and I'll be sitting their whining about how Valve took my hats... again.

And I'll be sitting here, being smug that VALVe just can't win.

FYI, it just creates a high FPS config that you can use on idle servers so you don't use as much electricity. :eng101:

Once Shugo gets online I'm gonna talk to him, but I'm preeeeeeetty sure this is going to be something people are going to be extremely cautious about. It gives players an "unfair advantage". "No it doesn't!" Guess what. SteamStats didn't! And look where it got you lot.

This is exactly the same as running tf2 :frogdowns:

This is still detectable. Not by any checksums or DLL lists, but by the stats system. TF2 records how long you've been playing, and all the various things you do. Valve can just look through the logs, see that in 8 hours you didn't move at all, and hit you with the hat hammer.

[quote]- Autoreconnect if you get disconnected[/quote] That was the only thing I liked about Steamstats.exe

I'll stick to normal idling ingame thanks than using scripts. I got accused of cheating but not actally caught and I dont want to be. I dont want Gabe coming after me on TF2 with his Ban Hammer.