When you idle with SourceTools, and you idle over night and get items, how do you add them to your back pack?
(Using Crypt n Lulz item system)
Source tools? What is that? Links now.
Go in TF2 and die and they should show up.
[QUOTE=Amaurus;23169016]Source tools? What is that? Links now.[/QUOTE]
[url]http://www.sourceop.com/modules.php?name=Forums&file=viewtopic&t=2292[/url]
Ahh Another idling program. I'll have to try it later.
I thought 3rd party idlers were considered cheating?
[QUOTE=johnlmonkey;23169331]I thought 3rd party idlers were considered cheating?[/QUOTE]
They are.
But this isn't a 3rd party idling program, all it does is put you on idle servers.
Isn't it essentially a different form of textmode idling?
Pretty much.
Just more fancy and shit.
[QUOTE=Uber_Tofu;23169888]But this isn't a 3rd party idling program, all it does is put you on idle servers.[/QUOTE]
That's what the other idler did too.
I can't seem to get a good list of servers for Source Tools to idle with, and I don't know how to start my own server in source tools, so I just have it windowed and I'm idling in my own listen server.
[QUOTE=Mexican;23169957]That's what the other idler did too.[/QUOTE]
This one isn't an EXE. It's just basically a really complex script. It creates a bunch of CFG files, and runs them.
DF's idler was an actual program, and that's what broke the rules.
[QUOTE=Mexican;23169957]That's what the other idler did too.[/QUOTE]
The major difference:
The old Steam Stats tool directly connected to an idle server, making them easily detectable.
This uses hl2.exe to connect to servers (The native TF2 program), making it virtually impossible to be detected.
Therefore, it is not a third party program connecting to servers, making this completely legal within Valve's TOS through a clever loophole.
oh alrighty then
clever
[QUOTE=SGTNAPALM;23169983]The major difference:
The old Steam Stats tool directly connected to an idle server, making them easily detectable.
This uses hl2.exe to connect to servers (The native TF2 program), making it virtually impossible to be detected.
Therefore, it is not a third party program connecting to servers, making this completely legal within Valve's TOS through a clever loophole.[/QUOTE]
:golfclap:
People are actually connecting to my idle server not knowing it's listen.
Oh well their fault.
[editline]12:49AM[/editline]
A lot of people. It's already full.
question. Can you play another steam game while source tools is doing its magic?
[QUOTE=Man in the Moon;23172122]question. Can you play another steam game while source tools is doing its magic?[/QUOTE]
If you idle in textmode, yes
and it won't mess up source tools at all?
no
[editline]03:16AM[/editline]
I mean nothing will go wrong.
fantastic, thank you.
[QUOTE=Hackintosh;23169177][url]http://www.sourceop.com/modules.php?name=Forums&file=viewtopic&t=2292[/url][/QUOTE]
If you get a "Client and Server Products do not match" or something error, it gets hung up and won't do anything. It happened after about 30 different server attempts (I added the huge list of idle server IPs he had a link to).
I made a thread asking for a link, just Google "sourcetools server list question", it's usually the first result, then scroll down until you see Firelash's answer. That's what I'm using.
[QUOTE=LastLucario;23173095]I made a thread asking for a link, just Google "sourcetools server list question", it's usually the first result, then scroll down until you see Firelash's answer. That's what I'm using.[/QUOTE]
I found that after adding a bunch of my own, and I think it was 220.253.91.8:27015 that gave me the error.
I just use an autoexec script that starts up its own server and turns sv_lan off when I go idling in textmode. Works reasonably well.
Sorry, you need to Log In to post a reply to this thread.
