i'd consider this news: fairly large tf2 update
+12
Taboo
Lord Zurkov
Havik
vladmirbsl69
Furgus
Epps
Eraserhead
Tendo
Young Greezy
ninji
Brother_
LOOK IT'S ADAM!!!
16 posters
Page 2 of 3
Page 2 of 3 • 1, 2, 3
Re: i'd consider this news: fairly large tf2 update
Nothing, you just shared it with us. Now all there is left to us is having it watched by one of us...
Re: i'd consider this news: fairly large tf2 update
Exia STEAM_0:1:22623760
http://pulpfortress.clanservers.com/tf2stats/id/STEAM_0:1:22623760
I warned this player Several times that this would earn them a ban, and guess what, they didn't listen.
Demo
http://www.mediafire.com/?jauoyymzino
Also, they were making the stuff as a spy, which is a terrible glitch.
http://pulpfortress.clanservers.com/tf2stats/id/STEAM_0:1:22623760
I warned this player Several times that this would earn them a ban, and guess what, they didn't listen.
Demo
http://www.mediafire.com/?jauoyymzino
Also, they were making the stuff as a spy, which is a terrible glitch.
Re: i'd consider this news: fairly large tf2 update
The nearly filled up the whole spawn just with dispensers.
btw What program do use to watch these files?
btw What program do use to watch these files?
Furgus- Clan Member
- Posts : 859
Join date : 2009-12-04
Age : 29
Location : New jersey, U.S.A
Re: i'd consider this news: fairly large tf2 update
Oh, it's against the server rules? I was screwing around with it before Valve gets around to patching it, but I didn't know it would constitute any sort of serious offense.
I even made a script to make it easier.
I even made a script to make it easier.
- Spoiler:
- Copy this, and paste it into a CFG file:
- Code:
alias "dispenser" "cyclenext0_00"; alias "cyclenext0_00" "build 0 0; alias dispenser cyclenext0_01"; alias "cyclenext0_01" "build 0 1; alias dispenser cyclenext0_02"; alias "cyclenext0_02" "build 0 2; alias dispenser cyclenext0_03"; alias "cyclenext0_03" "build 0 3; alias dispenser cyclenext0_04"; alias "cyclenext0_04" "build 0 4; alias dispenser cyclenext0_05"; alias "cyclenext0_05" "build 0 5; alias dispenser cyclenext0_06"; alias "cyclenext0_06" "build 0 6; alias dispenser cyclenext0_07"; alias "cyclenext0_07" "build 0 7; alias dispenser cyclenext0_08"; alias "cyclenext0_08" "build 0 8; alias dispenser cyclenext0_09"; alias "cyclenext0_09" "build 0 9; alias dispenser cyclenext0_10"; alias "cyclenext0_10" "build 0 10; alias dispenser cyclenext0_11"; alias "cyclenext0_11" "build 0 11; alias dispenser cyclenext0_12"; alias "cyclenext0_12" "build 0 12; alias dispenser cyclenext0_13"; alias "cyclenext0_13" "build 0 13; alias dispenser cyclenext0_14"
alias "cyclenext0_14" "build 0 14; alias dispenser cyclenext0_15"; alias "cyclenext0_15" "build 0 15; alias dispenser cyclenext0_16"; alias "cyclenext0_16" "build 0 16; alias dispenser cyclenext0_17"; alias "cyclenext0_17" "build 0 17; alias dispenser cyclenext0_18"; alias "cyclenext0_18" "build 0 18; alias dispenser cyclenext0_19"; alias "cyclenext0_19" "build 0 19; alias dispenser cyclenext0_20"; alias "cyclenext0_20" "build 0 20; alias dispenser cyclenext0_21"; alias "cyclenext0_21" "build 0 21; alias dispenser cyclenext0_22"; alias "cyclenext0_22" "build 0 22; alias dispenser cyclenext0_23"; alias "cyclenext0_23" "build 0 23; alias dispenser cyclenext0_24"; alias "cyclenext0_24" "build 0 24; alias dispenser cyclenext0_25"; alias "cyclenext0_25" "build 0 25; alias dispenser cyclenext0_26"; alias "cyclenext0_26" "build 0 26; alias dispenser cyclenext0_27"; alias "cyclenext0_27" "build 0 27; alias dispenser cyclenext0_28"; alias "cyclenext0_28" "build 0 28; alias dispenser cyclenext0_29"
alias "cyclenext0_29" "build 0 29; alias dispenser cyclenext0_30"; alias "cyclenext0_30" "build 0 30; alias dispenser cyclenext0_31"; alias "cyclenext0_31" "build 0 31; alias dispenser cyclenext0_32"; alias "cyclenext0_32" "build 0 32; alias dispenser cyclenext0_33"; alias "cyclenext0_33" "build 0 33; alias dispenser cyclenext0_34"; alias "cyclenext0_34" "build 0 34; alias dispenser cyclenext0_35"; alias "cyclenext0_35" "build 0 35; alias dispenser cyclenext0_36"; alias "cyclenext0_36" "build 0 36; alias dispenser cyclenext0_37"; alias "cyclenext0_37" "build 0 37; alias dispenser cyclenext0_38"; alias "cyclenext0_38" "build 0 38; alias dispenser cyclenext0_39"; alias "cyclenext0_39" "build 0 39; alias dispenser cyclenext0_40"; alias "cyclenext0_40" "build 0 40; alias dispenser cyclenext0_41"; alias "cyclenext0_41" "build 0 41; alias dispenser cyclenext0_42"; alias "cyclenext0_42" "build 0 42; alias dispenser cyclenext0_43"; alias "cyclenext0_43" "build 0 43; alias dispenser cyclenext0_44"
alias "cyclenext0_44" "build 0 44; alias dispenser cyclenext0_45"; alias "cyclenext0_45" "build 0 45; alias dispenser cyclenext0_46"; alias "cyclenext0_46" "build 0 46; alias dispenser cyclenext0_47"; alias "cyclenext0_47" "build 0 47; alias dispenser cyclenext0_48"; alias "cyclenext0_48" "build 0 48; alias dispenser cyclenext0_49"; alias "cyclenext0_49" "build 0 49; alias dispenser cyclenext0_50"; alias "cyclenext0_50" "build 0 50; alias dispenser cyclenext0_51"; alias "cyclenext0_51" "build 0 51; alias dispenser cyclenext0_52"; alias "cyclenext0_52" "build 0 52; alias dispenser cyclenext0_53"; alias "cyclenext0_53" "build 0 53; alias dispenser cyclenext0_54"; alias "cyclenext0_54" "build 0 54; alias dispenser cyclenext0_55"; alias "cyclenext0_55" "build 0 55; alias dispenser cyclenext0_56"; alias "cyclenext0_56" "build 0 56; alias dispenser cyclenext0_57"; alias "cyclenext0_57" "build 0 57; alias dispenser cyclenext0_58"; alias "cyclenext0_58" "build 0 58; alias dispenser cyclenext0_59"
alias "cyclenext0_59" "build 0 59; alias dispenser cyclenext0_60"; alias "cyclenext0_60" "build 0 60; alias dispenser cyclenext0_61"; alias "cyclenext0_61" "build 0 61; alias dispenser cyclenext0_62"; alias "cyclenext0_62" "build 0 62; alias dispenser cyclenext0_63"; alias "cyclenext0_63" "build 0 63; alias dispenser cyclenext0_64"; alias "cyclenext0_64" "build 0 64; alias dispenser cyclenext0_65"; alias "cyclenext0_65" "build 0 65; alias dispenser cyclenext0_66"; alias "cyclenext0_66" "build 0 66; alias dispenser cyclenext0_67"; alias "cyclenext0_67" "build 0 67; alias dispenser cyclenext0_68"; alias "cyclenext0_68" "build 0 68; alias dispenser cyclenext0_69"; alias "cyclenext0_69" "build 0 69; alias dispenser cyclenext0_70"; alias "cyclenext0_70" "build 0 70; alias dispenser cyclenext0_71"; alias "cyclenext0_71" "build 0 71; alias dispenser cyclenext0_72"; alias "cyclenext0_72" "build 0 72; alias dispenser cyclenext0_73"; alias "cyclenext0_73" "build 0 73; alias dispenser cyclenext0_74"
alias "cyclenext0_74" "build 0 74; alias dispenser cyclenext0_75"; alias "cyclenext0_75" "build 0 75; alias dispenser cyclenext0_76"; alias "cyclenext0_76" "build 0 76; alias dispenser cyclenext0_77"; alias "cyclenext0_77" "build 0 77; alias dispenser cyclenext0_78"; alias "cyclenext0_78" "build 0 78; alias dispenser cyclenext0_79"; alias "cyclenext0_79" "build 0 79; alias dispenser cyclenext0_80"; alias "cyclenext0_80" "build 0 80; alias dispenser cyclenext0_81"; alias "cyclenext0_81" "build 0 81; alias dispenser cyclenext0_82"; alias "cyclenext0_82" "build 0 82; alias dispenser cyclenext0_83"; alias "cyclenext0_83" "build 0 83; alias dispenser cyclenext0_84"; alias "cyclenext0_84" "build 0 84; alias dispenser cyclenext0_85"; alias "cyclenext0_85" "build 0 85; alias dispenser cyclenext0_86"; alias "cyclenext0_86" "build 0 86; alias dispenser cyclenext0_87"; alias "cyclenext0_87" "build 0 87; alias dispenser cyclenext0_88"; alias "cyclenext0_88" "build 0 88; alias dispenser cyclenext0_89"
alias "cyclenext0_89" "build 0 89; alias dispenser cyclenext0_90"; alias "cyclenext0_90" "build 0 90; alias dispenser cyclenext0_91"; alias "cyclenext0_91" "build 0 91; alias dispenser cyclenext0_92"; alias "cyclenext0_92" "build 0 92; alias dispenser cyclenext0_93"; alias "cyclenext0_93" "build 0 93; alias dispenser cyclenext0_94"; alias "cyclenext0_94" "build 0 94; alias dispenser cyclenext0_95"; alias "cyclenext0_95" "build 0 95; alias dispenser cyclenext0_96"; alias "cyclenext0_96" "build 0 96; alias dispenser cyclenext0_97"; alias "cyclenext0_97" "build 0 97; alias dispenser cyclenext0_98"; alias "cyclenext0_98" "build 0 98; alias dispenser cyclenext0_99"; alias "cyclenext0_99" "build 0 99; alias dispenser cyclenext0_00"
alias "sentry" "cyclenext2_00"; alias "cyclenext2_00" "build 2 0; alias sentry cyclenext2_01"; alias "cyclenext2_01" "build 2 1; alias sentry cyclenext2_02"; alias "cyclenext2_02" "build 2 2; alias sentry cyclenext2_03"; alias "cyclenext2_03" "build 2 3; alias sentry cyclenext2_04"; alias "cyclenext2_04" "build 2 4; alias sentry cyclenext2_05"; alias "cyclenext2_05" "build 2 5; alias sentry cyclenext2_06"; alias "cyclenext2_06" "build 2 6; alias sentry cyclenext2_07"; alias "cyclenext2_07" "build 2 7; alias sentry cyclenext2_08"; alias "cyclenext2_08" "build 2 8; alias sentry cyclenext2_09"; alias "cyclenext2_09" "build 2 9; alias sentry cyclenext2_10"; alias "cyclenext2_10" "build 2 10; alias sentry cyclenext2_11"; alias "cyclenext2_11" "build 2 11; alias sentry cyclenext2_12"; alias "cyclenext2_12" "build 2 12; alias sentry cyclenext2_13"; alias "cyclenext2_13" "build 2 13; alias sentry cyclenext2_14"; alias "cyclenext2_14" "build 2 14; alias sentry cyclenext2_15"
alias "cyclenext2_15" "build 2 15; alias sentry cyclenext2_16"; alias "cyclenext2_16" "build 2 16; alias sentry cyclenext2_17"; alias "cyclenext2_17" "build 2 17; alias sentry cyclenext2_18"; alias "cyclenext2_18" "build 2 18; alias sentry cyclenext2_19"; alias "cyclenext2_19" "build 2 19; alias sentry cyclenext2_20"; alias "cyclenext2_20" "build 2 20; alias sentry cyclenext2_21"; alias "cyclenext2_21" "build 2 21; alias sentry cyclenext2_22"; alias "cyclenext2_22" "build 2 22; alias sentry cyclenext2_23"; alias "cyclenext2_23" "build 2 23; alias sentry cyclenext2_24"; alias "cyclenext2_24" "build 2 24; alias sentry cyclenext2_25"; alias "cyclenext2_25" "build 2 25; alias sentry cyclenext2_26"; alias "cyclenext2_26" "build 2 26; alias sentry cyclenext2_27"; alias "cyclenext2_27" "build 2 27; alias sentry cyclenext2_28"; alias "cyclenext2_28" "build 2 28; alias sentry cyclenext2_29"; alias "cyclenext2_29" "build 2 29; alias sentry cyclenext2_30"; alias "cyclenext2_30" "build 2 30; alias sentry cyclenext2_31"
alias "cyclenext2_31" "build 2 31; alias sentry cyclenext2_32"; alias "cyclenext2_32" "build 2 32; alias sentry cyclenext2_33"; alias "cyclenext2_33" "build 2 33; alias sentry cyclenext2_34"; alias "cyclenext2_34" "build 2 34; alias sentry cyclenext2_35"; alias "cyclenext2_35" "build 2 35; alias sentry cyclenext2_36"; alias "cyclenext2_36" "build 2 36; alias sentry cyclenext2_37"; alias "cyclenext2_37" "build 2 37; alias sentry cyclenext2_38"; alias "cyclenext2_38" "build 2 38; alias sentry cyclenext2_39"; alias "cyclenext2_39" "build 2 39; alias sentry cyclenext2_40"; alias "cyclenext2_40" "build 2 40; alias sentry cyclenext2_41"; alias "cyclenext2_41" "build 2 41; alias sentry cyclenext2_42"; alias "cyclenext2_42" "build 2 42; alias sentry cyclenext2_43"; alias "cyclenext2_43" "build 2 43; alias sentry cyclenext2_44"; alias "cyclenext2_44" "build 2 44; alias sentry cyclenext2_45"; alias "cyclenext2_45" "build 2 45; alias sentry cyclenext2_46"; alias "cyclenext2_46" "build 2 46; alias sentry cyclenext2_47"
alias "cyclenext2_47" "build 2 47; alias sentry cyclenext2_48"; alias "cyclenext2_48" "build 2 48; alias sentry cyclenext2_49"; alias "cyclenext2_49" "build 2 49; alias sentry cyclenext2_50"; alias "cyclenext2_50" "build 2 50; alias sentry cyclenext2_51"; alias "cyclenext2_51" "build 2 51; alias sentry cyclenext2_52"; alias "cyclenext2_52" "build 2 52; alias sentry cyclenext2_53"; alias "cyclenext2_53" "build 2 53; alias sentry cyclenext2_54"; alias "cyclenext2_54" "build 2 54; alias sentry cyclenext2_55"; alias "cyclenext2_55" "build 2 55; alias sentry cyclenext2_56"; alias "cyclenext2_56" "build 2 56; alias sentry cyclenext2_57"; alias "cyclenext2_57" "build 2 57; alias sentry cyclenext2_58"; alias "cyclenext2_58" "build 2 58; alias sentry cyclenext2_59"; alias "cyclenext2_59" "build 2 59; alias sentry cyclenext2_60"; alias "cyclenext2_60" "build 2 60; alias sentry cyclenext2_61"; alias "cyclenext2_61" "build 2 61; alias sentry cyclenext2_62"; alias "cyclenext2_62" "build 2 62; alias sentry cyclenext2_63"
alias "cyclenext2_63" "build 2 63; alias sentry cyclenext2_64"; alias "cyclenext2_64" "build 2 64; alias sentry cyclenext2_65"; alias "cyclenext2_65" "build 2 65; alias sentry cyclenext2_66"; alias "cyclenext2_66" "build 2 66; alias sentry cyclenext2_67"; alias "cyclenext2_67" "build 2 67; alias sentry cyclenext2_68"; alias "cyclenext2_68" "build 2 68; alias sentry cyclenext2_69"; alias "cyclenext2_69" "build 2 69; alias sentry cyclenext2_70"; alias "cyclenext2_70" "build 2 70; alias sentry cyclenext2_71"; alias "cyclenext2_71" "build 2 71; alias sentry cyclenext2_72"; alias "cyclenext2_72" "build 2 72; alias sentry cyclenext2_73"; alias "cyclenext2_73" "build 2 73; alias sentry cyclenext2_74"; alias "cyclenext2_74" "build 2 74; alias sentry cyclenext2_75"; alias "cyclenext2_75" "build 2 75; alias sentry cyclenext2_76"; alias "cyclenext2_76" "build 2 76; alias sentry cyclenext2_77"; alias "cyclenext2_77" "build 2 77; alias sentry cyclenext2_78"; alias "cyclenext2_78" "build 2 78; alias sentry cyclenext2_79"
alias "cyclenext2_79" "build 2 79; alias sentry cyclenext2_80"; alias "cyclenext2_80" "build 2 80; alias sentry cyclenext2_81"; alias "cyclenext2_81" "build 2 81; alias sentry cyclenext2_82"; alias "cyclenext2_82" "build 2 82; alias sentry cyclenext2_83"; alias "cyclenext2_83" "build 2 83; alias sentry cyclenext2_84"; alias "cyclenext2_84" "build 2 84; alias sentry cyclenext2_85"; alias "cyclenext2_85" "build 2 85; alias sentry cyclenext2_86"; alias "cyclenext2_86" "build 2 86; alias sentry cyclenext2_87"; alias "cyclenext2_87" "build 2 87; alias sentry cyclenext2_88"; alias "cyclenext2_88" "build 2 88; alias sentry cyclenext2_89"; alias "cyclenext2_89" "build 2 89; alias sentry cyclenext2_90"; alias "cyclenext2_90" "build 2 90; alias sentry cyclenext2_91"; alias "cyclenext2_91" "build 2 91; alias sentry cyclenext2_92"; alias "cyclenext2_92" "build 2 92; alias sentry cyclenext2_93"; alias "cyclenext2_93" "build 2 93; alias sentry cyclenext2_94"; alias "cyclenext2_94" "build 2 94; alias sentry cyclenext2_95"
alias "cyclenext2_95" "build 2 95; alias sentry cyclenext2_96"; alias "cyclenext2_96" "build 2 96; alias sentry cyclenext2_97"; alias "cyclenext2_97" "build 2 97; alias sentry cyclenext2_98"; alias "cyclenext2_98" "build 2 98; alias sentry cyclenext2_99"; alias "cyclenext2_99" "build 2 99; alias sentrysentry cyclenext2_00"
It pulls out up to 100 dispensers and 100 sentries.
Last edited by Lord Zurkov on 29/4/2010, 21:01; edited 1 time in total
Lord Zurkov- Clan Member
- Posts : 402
Join date : 2010-01-09
Age : 33
Re: i'd consider this news: fairly large tf2 update
That looks totally awesome, if i was playing i would so do the same. I really don't think this should be a bannable offence but that's just my opinion. Why ban someone for something that they won't be able to do in the next week or so? It's just as zurkov said, just messing around, having a fun time! lol
Taboo- Acting Game Admin
- Posts : 179
Join date : 2009-12-07
Age : 32
Re: i'd consider this news: fairly large tf2 update
Guys you are forgetting sourcebans. I don't think banning still works but i didn't test it. I see the sourcebans dashboard still has connectivity with the server, so that's a good thing:
http://pulpfortress.clanservers.com/sourcebans/index.php?p=home
After logging in with my account (all you admins have accounts!) i could rightclick the active players and select kick or ban. With sourcebans you can even upload demo's! (never tried it before though)
Also simply reporting playernames isn't enough, we need steam ID's or steam profile pages. I did see some ID's coming by in this thread so this remark is not for everyone.
So admins please try to ban a player next time via the sourcebans webpage, while ingame you should just go to www.pulpfortress.com and click sourcebans and login.
PS: I love the screenshots of all the sentries
Even if a player isn't banned immediately it's still worth registering the ban via sourcebans because as soon as sourcemod is fixed it will work again and ban that player on our servers.
Also i can still kick players via HLSW admin tool, only ban doesn't work. Also tried the console command but nothing happened. I'm looking for an alternative admin tool right now...
http://pulpfortress.clanservers.com/sourcebans/index.php?p=home
After logging in with my account (all you admins have accounts!) i could rightclick the active players and select kick or ban. With sourcebans you can even upload demo's! (never tried it before though)
Also simply reporting playernames isn't enough, we need steam ID's or steam profile pages. I did see some ID's coming by in this thread so this remark is not for everyone.
So admins please try to ban a player next time via the sourcebans webpage, while ingame you should just go to www.pulpfortress.com and click sourcebans and login.
PS: I love the screenshots of all the sentries
Even if a player isn't banned immediately it's still worth registering the ban via sourcebans because as soon as sourcemod is fixed it will work again and ban that player on our servers.
Also i can still kick players via HLSW admin tool, only ban doesn't work. Also tried the console command but nothing happened. I'm looking for an alternative admin tool right now...
Re: i'd consider this news: fairly large tf2 update
this is what happens when the admins let it go.
the server crashed a few minutes afterwards when they tried to destroy everything at once.
the server crashed a few minutes afterwards when they tried to destroy everything at once.
LOOK IT'S ADAM!!!- Clan Member
- Posts : 511
Join date : 2010-02-16
Age : 34
Location : Cal Poly, the real one.
Re: i'd consider this news: fairly large tf2 update
I'm gonna speak up for the guy who's not being defended by anyone.
Pulp members have been caught doing the same thing, though I won't name names. The game right now is a complete mess of exploits, why not just let it get fixed and move on? It's not like it's effecting anyone's precious rank--that isn't working either.
Edit:
http://forum.pulpfortress.com/news-f1/i-d-consider-this-news-fairly-large-tf2-update-t702.htm
Run down that post and count the number of Pulp members complaining that they can't perform their personal favorite exploit/glitch proportional to the posts made.
Edit2: That's funny, that link actually got merged with the topic we were originally on.
Pulp members have been caught doing the same thing, though I won't name names. The game right now is a complete mess of exploits, why not just let it get fixed and move on? It's not like it's effecting anyone's precious rank--that isn't working either.
Edit:
http://forum.pulpfortress.com/news-f1/i-d-consider-this-news-fairly-large-tf2-update-t702.htm
Run down that post and count the number of Pulp members complaining that they can't perform their personal favorite exploit/glitch proportional to the posts made.
Edit2: That's funny, that link actually got merged with the topic we were originally on.
Last edited by The Mad Hatter on 29/4/2010, 22:00; edited 1 time in total
The Mad Hatter- Attention whore
- Posts : 239
Join date : 2010-04-14
Age : 39
Re: i'd consider this news: fairly large tf2 update
A snapshot release of sourcemod and metamod have come out which seem to fix almost everything. Only the custom hats are not working and i'm unsure about the ranking plugin. I will have updated both servers soon, i'm working on the VIP server now...
PS: I merged this with adams topic about the update coming out because it's basically all related.
edit: I just updated the VIP server with latest sourcemod and metamod but the admin menu still isn't working. I guess we have to wait till tomorrow when the stable release comes out. Also i expect valve to come with a fix for the engies tomorrow.
PS: I merged this with adams topic about the update coming out because it's basically all related.
edit: I just updated the VIP server with latest sourcemod and metamod but the admin menu still isn't working. I guess we have to wait till tomorrow when the stable release comes out. Also i expect valve to come with a fix for the engies tomorrow.
Re: i'd consider this news: fairly large tf2 update
this just out.
- Added new items to commemorate our 119th (or so) update.
- Fixed several issues with the Source SDK
- Scout's "Retire the Runner" achievement updated to be:
- "Kill a Scout while they are under the effect of Crit-a-Cola."
- Added a 20% damage bonus to The Backburner
- Fixed the Flare Gun's afterburn duration being lowered by the Flamethrower's duration reduction
- Fixed the teleporter exit using the wrong particle effect
- Fixed HUD damage indicators not appearing
- Fixed Teleporters not reverting to level 1 when their other side is destroyed
- Fixed receiving damage not causing view-kicks on players
- Fixed Engineers & Spies being able to circumvent build restrictions
- Fixed Server Browser not saving filter settings properly
- Fixed a client crash in the targetID on clients running custom HUDs
- Added new items to commemorate our 119th (or so) update.
- Fixed several issues with the Source SDK
- Scout's "Retire the Runner" achievement updated to be:
- "Kill a Scout while they are under the effect of Crit-a-Cola."
- Added a 20% damage bonus to The Backburner
- Fixed the Flare Gun's afterburn duration being lowered by the Flamethrower's duration reduction
- Fixed the teleporter exit using the wrong particle effect
- Fixed HUD damage indicators not appearing
- Fixed Teleporters not reverting to level 1 when their other side is destroyed
- Fixed receiving damage not causing view-kicks on players
- Fixed Engineers & Spies being able to circumvent build restrictions
- Fixed Server Browser not saving filter settings properly
- Fixed a client crash in the targetID on clients running custom HUDs
LOOK IT'S ADAM!!!- Clan Member
- Posts : 511
Join date : 2010-02-16
Age : 34
Location : Cal Poly, the real one.
Re: i'd consider this news: fairly large tf2 update
Jameless performed this update on our servers, so no more engie exploits!
Re: i'd consider this news: fairly large tf2 update
Yeah I noticed it, TF2 was downloading once again. Best part of the update: "Fixed Engineers & Spies being able to circumvent build restrictions.".
As for the exploiting, if my admin panel was working yesterday I would have warned the players exploiting and I might as well banned them if they ignored my orders and yes, this includes clanmembers. Wait, ryou would ban a clanmember?!
Yes I would because I would expect them to be serious players, wanna enjoy the exploiting go to the VIP server but dont do it on a public server where you are screwing people over who just want to play the game.
As for the exploiting, if my admin panel was working yesterday I would have warned the players exploiting and I might as well banned them if they ignored my orders and yes, this includes clanmembers. Wait, ryou would ban a clanmember?!
Yes I would because I would expect them to be serious players, wanna enjoy the exploiting go to the VIP server but dont do it on a public server where you are screwing people over who just want to play the game.
Re: i'd consider this news: fairly large tf2 update
YES FINALLY!!!!!!!!!!! And yeah some of the members/applicants were doing the same thing but they stopped after awhile. Others just kept going. And I can finally work on my new map coming up.
Furgus- Clan Member
- Posts : 859
Join date : 2009-12-04
Age : 29
Location : New jersey, U.S.A
Re: i'd consider this news: fairly large tf2 update
Btw I have been having some problems with tf2 recently. And was wondering if it was because of the update.
1. So when I'm capping a point or just running around. I don't see the little squares at the bottom. The squares at the bottom used to show me. IF a control point was captured by the red or blue.
2. Every time now since the update. When I go in Tf2. I've had to readjust my resolution every time I go on tf2. The resolution is always at wide screen and and a resolution that makes everything big. My normal resolution is where it's normal screen and the letters are medium sized.
Could anyone help me with this? Should I just reinstall tf2?
1. So when I'm capping a point or just running around. I don't see the little squares at the bottom. The squares at the bottom used to show me. IF a control point was captured by the red or blue.
2. Every time now since the update. When I go in Tf2. I've had to readjust my resolution every time I go on tf2. The resolution is always at wide screen and and a resolution that makes everything big. My normal resolution is where it's normal screen and the letters are medium sized.
Could anyone help me with this? Should I just reinstall tf2?
Furgus- Clan Member
- Posts : 859
Join date : 2009-12-04
Age : 29
Location : New jersey, U.S.A
Re: i'd consider this news: fairly large tf2 update
FYI, the engie exploit is not fixed, and more and more people know how to do it.
LOOK IT'S ADAM!!!- Clan Member
- Posts : 511
Join date : 2010-02-16
Age : 34
Location : Cal Poly, the real one.
TF2 Update #119
In response to the veteran's medals included in the update:
The reason we got the Orange Box on his account instead of mine was because he'd get more playtime out of the other four games than I would (which wasn't very much).
Lord Zurkov wrote:FFFFFFFFFFFFFFFFFFFFFFFFFUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU——
I've been with TF2 since the beta, but I spent a hell of a lot of that time on my brother's account. He's gonna get a medal that shows how committed he is... and he plays so rarely that the last time I checked he hadn't even gotten on long enough to claim his Cheater's Lament yet. -_-
I feel like Valve robbed me. Again.Lord Zurkov wrote:TF2 was released on October 10, 2007. Steam says my brother bought his on Oct 9, 2007 (he had pre-ordered it, so we got to take part in the beta). He hardly ever played it though, so I used his account. After all, it'd be stupid to buy the game twice if only one person is using it, right?
...right? Well, when I eventually got TF2 on my account, it was purchased May 7, 2008. Then this happens.
Goddamnit, Valve.
The reason we got the Orange Box on his account instead of mine was because he'd get more playtime out of the other four games than I would (which wasn't very much).
Last edited by Lord Zurkov on 30/4/2010, 13:19; edited 1 time in total
Lord Zurkov- Clan Member
- Posts : 402
Join date : 2010-01-09
Age : 33
Re: i'd consider this news: fairly large tf2 update
@Adam: Do you mean the update didn't fix it? Or our servers aren't fixed?
jameless- Senior Game Admin
- Posts : 955
Join date : 2010-01-04
Age : 42
Location : Florida
Re: i'd consider this news: fairly large tf2 update
Our servers arn't fixed!
Jonesie|UKCS|- I am banned, sad face! Unban me! I don't deserve it !
- Posts : 1378
Join date : 2010-01-16
Age : 29
Location : Worcester
Re: i'd consider this news: fairly large tf2 update
Can anyone test if anyone else's servers are still doing the engy exploit because I installed the update that was supposed to fix this.
jameless- Senior Game Admin
- Posts : 955
Join date : 2010-01-04
Age : 42
Location : Florida
Re: i'd consider this news: fairly large tf2 update
the update didn't fix it. there is a way to get around the fix, i won't say it here, but PM me if you want the details.
ADAM- Guest
Re: i'd consider this news: fairly large tf2 update
damn, can't edit as guest. anyways, i can confirm that this is still a problem on all servers, my server still allowed a modified version of the exploit to happen. curious, i went over to the PULP server and tested it there, it still happens. so if you get complaints about me building 6 dispensers in the spawn, you know why. i went to a couple other servers and discovered there is a sourcemod plugin that fixes the problem in a roundabout fashion(by kicking/banning the user). it was sent out to the windows hlds list:
however, i think that injecting Bl4nk's engineer building destroyer plugin into this new one would provide a better solution by destroying the buildings instead of kicking the player.
however, i think that injecting Bl4nk's engineer building destroyer plugin into this new one would provide a better solution by destroying the buildings instead of kicking the player.
ADAM- Guest
Re: i'd consider this news: fairly large tf2 update
Ok thanks for this. I will msg you on steam.
yea we have that engy destroy plugin but we can't get sourcemod to work properly.
yea we have that engy destroy plugin but we can't get sourcemod to work properly.
jameless- Senior Game Admin
- Posts : 955
Join date : 2010-01-04
Age : 42
Location : Florida
Re: i'd consider this news: fairly large tf2 update
Yeah today when I was in the server this guy called Pokemon Master was building dispensers and sentries. And was suing a different method. Which is really similar to the original method.
Furgus- Clan Member
- Posts : 859
Join date : 2009-12-04
Age : 29
Location : New jersey, U.S.A
Page 2 of 3 • 1, 2, 3
Similar topics
» Engineer Update news!!
» How large is YOUR backlog?
» Engineer update
» Important news: PULP is merging with cCc!
» TF2 Update
» How large is YOUR backlog?
» Engineer update
» Important news: PULP is merging with cCc!
» TF2 Update
Page 2 of 3
Permissions in this forum:
You cannot reply to topics in this forum