Food $200
Data $150
Rent $800
American Flags $3,600
Utility $150
someone who is good at the economy please help me budget this. my family is dying

I'm running a server for him, so all the players are mang0 viewers & subs.

EDIT: Speaking of which, if anyone has suggestions for additions to the server, don't hesitate to tell me.
I'm currently planning on setting up reserved/hidden slots for mang0 subs and mods.

there is a new build for the plugin available here which works on the latest version of TF2, if anyone is still interested in testing this for 6s

hi i sign up

alias = sndrec
regfion = east coast

http://puu.sh/iRpXC/efe9256594.png

I just finished playing in the latest NA Practice Tournament for TF2 with some friends, and I have a few comments on the server and match performance.

First of all, the issues mentioned in the thread previously are pretty obvious: fade-to-black, and the buggy ready-up plugin. Simple enough to fix, I reckon, and not all that impactful on the game as a whole.

The server locations, however, are not ideal - US Central servers are probably, as suggested by saam, a better way to go. With the LA based server we played both of our matches on, most of my teammates (as well as myself) were experiencing pings above 100. A couple of us were also experiencing severe lag-spikes that prevented them from playing to their full ability.

I'm looking forward to seeing these issues resolved, as Razer Arena seems much easier to use and far more accessible than other avenues of TF2 competitive, with its great design both in game and on the website as well as active administrator support before or during games (something sorely lacking in other leagues)

Best of luck to you folks - I'll definitely be playing here in the future.

yeah @wareya i do appreciate the reality checks from someone who knows the engine better than i - i might've gotten overhyped about posting this thread after having such positive results in testing with hit registration

regardless, i would still like to see 128 tick 6s pugs take place to see how it affects games, and i encourage anyone who has the resources to set something like that up to please do so

If this is the case, then why can't we push Valve to implement similar fixes into TF2?

Perhaps we could see them with the up-and-coming matchmaking update that's been All The Excitement in the community lately. It's something I think this community should aim for - since 128 tick makes aiming better, after all

..get it??

The door speed is the major issue right now - but yes, you only need to divide the new tickrate by 66 in order to get the ratio required to speed doors up by. Actually making them open faster is another deal entirely - I don't know how possible that is through a server plugin.

Sorry - I've rewritten that part now. I realize that re-reading it, it sounds too opinionated. As I've put at the bottom of the OP, I want to help this community - CSGO has reaped the benefits of 128 tick for a while, and I think we need to push to have it in TF2 as well, if it's possible.

I've read the linked article before, and I've studied the mechanics of airstrafing/bunny hopping pretty intensely - I didn't think the effects of high tickrate on airstrafing would make any extreme difference in gameplay, but that's why I want to do more wide-scale testing. We'll never find out if this is viable for competitive play if we don't try it.

Really? I thought that the default value of sv_airaccelerate 10 would cap airstrafing at a certain level of control regardless of how high you push the tickrate.

There's a strict 1.2x max speed limit when bhopping, and that's when landing tick perfect jumps - otherwise you're instantly capped to your normal speed. It's a strict cap in the code. The effects on airstrafing and fall speed are minimal enough to only really be noticeable in intense movement modes like surf and bhop.

I'm aware that it'll never be perfect, but I wasn't able to notice any difference with the game mechanics when I was testing - this is why the thread was made though, so that more large-scale testing could be done.

I've found that increasing the minimum cmdrate and updaterate to 128 can force clients to values higher than 100. Try it out!

The engine is designed to intelligently scale almost every game mechanic with the tickrate. The only major negative difference I've noticed after lots of testing is the change in door speed.

Doors opening slowly can probably be fixed easily with a plugin (maybe modify the tickrate enabler source code for a tf2 specific version?), but I don't know about the rate caps. I'd like if someone who's well versed with writing plugins for the engine could comment on the subject

Yes, but you still need access to the server launch parameters to adjust tickrate - you can't change it through any cvar, and the only thing this plugin does is unlock the launch parameter.

I understand your concern though, and I definitely don't condone people trying to squeeze more performance out of server providers than they pay for - a tickrate of 128 is effectively doubling the CPU use and bandwidth of your server, and will negatively effect your server provider if you're not certain it's something you can do.