Anyway, unless YOU tell us that you've run a server and idled SOLO
I don't have to, I have multiple remote servers at datacenters, why would I waste my time?
There are maney a reasons why thou, a gentle manne, could waste thou time.
Remote server connection is never 100% permanent. If you leave for an extended period of time [days], you risk being disconnected and waste whatever time not idling until you come back.
As for if ever VALVe decides to blacklist achievement idle servers, you can always hide behind your "legit" empty 2fort server
Then again, I guess you can idle all you want on your server even if it's not an idle server.
Anyway, you seemed to be suggesting that it was a router setup issue, hence knowing what there was to do to allow drops on a private server.
You told nirvaa that his router problem isn't just about forwarding, but his problem isn't about having his connection dropped by the router. It's about running a TF2 server behind a router that would fit whatever criteria needed for giving the sole player in it some item drops.
You told nirvaa that his router problem isn't just about forwarding, but his problem isn't about having his connection dropped by the router. It's about running a TF2 server behind a router that would fit whatever criteria needed for giving the sole player in it some item drops.
Actually, I know how to run a TF2 server behind a router, as a sole player, and get some item drops. Some meaning far reduced from the rate on a server full of people (be they idling or actually playing).
What I need to know is how to get the normal rate of item drops, as a sole player on a server behind a router. I really don't think the router has anything to do with it.
Posted: Mon Oct 05, 2009 2:19 pm Post subject: AUTO RECONNECT SCRIPT BETA
Currently broken until further notice
I have completed a script to auto reconnect shortly after being disconnected [either from losing the connection to the internet, or being kicked, or server timed out, etc]
This script will initiate a "retry" attempt. I haven't gotten around to making it cycle through a list. So if the server you were connected to has crashed and isn't coming back up, you'll be SOL until that server comes back up.
It is still in beta as I will need to work out any bugs that arises. So for those who will try it, I will need your console dump if you got disconnected and didn't get reconnected.
Okay, here's how to do it [only works if you have walked through my guide already]:
MODE.BAT
Simply fill out your steamfolder, username and your launch options. Just 3 lines to modify for yourself, they are seen at the top with #####
To launch mode.bat, you need to specify either "idle" or "play"
so in command, you'd do this : mode.bat idle
or : mode.bat play
You can figure out how to do that with shortcuts as well.
Quote:
@echo off
##Steam folder location
##Example: C:\program files (x86)\steam [do not put an ending \ ]
set steamfolder=d:\steam
//Steam Username
//Username used to login, so that the program knows where you cfg files are.
set steamuser=steamlogin
the autorecon.cfg file will be automatically created by mode.bat
If you wanna test out the autoreconnect script, do the following :
1. load up TF2 in idle mode [mode.bat idle]
2. Wait for everything to load and connected to any idle server.
3. Wait about 1 minute for the mode.bat file to start checking your connection status.
4. Now, type disconnect in console. It will not autoreconnect because you weren't FORCED to disconnect
6. To simulate having been disconnected, type [ echo "disconnect:" ] in the console [don't forget the : ] This will write "disconnect:" in your console, which is what mode.bat will check.
7. sit and wait. Mode.bat will display "reconnecting..." and a few seconds later, TF2 will reconnect.
No time to explain it all how it works, I gtg, hope this will get positive results and decent feedback so I can tweak it.
note - You'll probably get a lot of junk appearing in the mode.bat window while you're connected. Don't worry about it, the script will still work. I gotta clean up the script a bit later.
Last edited by DispenserGUM on Mon Oct 05, 2009 9:23 pm; edited 4 times in total
You have "D:\steam" multiple places in your script. I believe this should be %steamfolder%
Thank you very much. That is why it's useful to have other people look at my work. I'm messy
I did a lot of the testing in separated batch files to isolate each problem, which made me have to type out my actual folder info since I didnt feel like copying all the variables in each batch file.. ugh....
well, anyway once this autoreconnect script is polished, I'm going to create another batch file that will pretty much setup everything for the user. You run it once, it will do EVERYTHING for you [backup your registry and server lists, create the shortcuts, etc]
Joined: Jan 02, 2005 Posts: 4131 Location: Spokane,WA
Posted: Mon Oct 05, 2009 5:50 pm Post subject:
DispenserGUM wrote:
Remote server connection is never 100% permanent. If you leave for an extended period of time [days], you risk being disconnected and waste whatever time not idling until you come back.
Remote server connection is never 100% permanent. If you leave for an extended period of time [days], you risk being disconnected and waste whatever time not idling until you come back.
It is more stable than my home computer.
good for you
the idle servers aren't always that stable though, then again, you're the elitist guy who runs several servers, so why don't you simply become aware that this guide doesn't apply to you?
The auto reconnect alias isn't activating itself until you click "OK" to the message of getting disconnected [timed out, kicked, whatever]
I might have to resort to shutting down TF2 the hard way upon getting disconnected and making it restart by connecting to an IP.... the long and ineffective way unless I can find a way to automate clicking "OK".
I thought the problem was the error window popup when you get disconnected. I couldnt figure out how to auto-close it to disable it.
Well, actually, it wasn't the problem. It was a simple synchronization problem between my batch and the script running within TF2. When the frame pops up, TF2's timing changes [you know, the "wait" command?]
I'll be fine tuning it today.
Hopefully, by tomorrow night, I'll have a self-installer batch for my guide. So pretty much everything will set itself up for you. No need to read through pages of steps
It will be ready for mass exportation!!
I thought the problem was the error window popup when you get disconnected. I couldnt figure out how to auto-close it to disable it.
Well, actually, it wasn't the problem. It was a simple synchronization problem between my batch and the script running within TF2. When the frame pops up, TF2's timing changes [you know, the "wait" command?]
I'll be fine tuning it today.
Hopefully, by tomorrow night, I'll have a self-installer batch for my guide. So pretty much everything will set itself up for you. No need to read through pages of steps
It will be ready for mass exportation!!
Then after, I will slowly be tweaking the autoreconnect features.
Right now, it will only reconnect you to the server you were previously on. So if that server has crashed permanently, you obviously won't be able to connect to it.
For any other disconnect the script will get you back on the server [as long as the server is connectable]
So you're covered if you got disconnected for : reserved slot, afk [i know some servers kick you after a few hours if you are in spectator], connection hiccup, whatever
For those impatient, or for those interested in testing right away in case there's a problem I havent noticed yet, here is mode.bat
MODE.BAT
Quote:
@echo off
set steamfolder=c:\program files\steam
set steamuser=steamlogin
set launchoptions=-novid +exec autoexec2.cfg
set timestamp=%date:~0,5% - %time:~0,8%
set error1=ResultNotLoggedOn
set error2=Connection failed
set error3=Server is full
set error4=disconnect:
set error5=Host_Error:
set error6=Server connection timed out
set connected=Connected to
set connecting=Connecting to
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum