How to launch 32-bit Team Fortress 2 and Join Casual/Community Servers

[Joey]

1. Go to the Team Fortress 2 main directory
2. Find "tf.exe"
3. Create a shortcut of "tf.exe"
4. Open the properties of the shortcut
6. Find targets and add -steam
7. Launch "tf.exe" via the Shortcut
You can now join vac secure servers with the 32-bit version of Team Fortress 2.

Mind you this WILL NOT work if you're using Windows 7 as the parameter isn't recognized.




As a sidenote;
I've got no clue if this is intentional, it doesn't seem to be.
It very likely will cease functioning once known or made aware of to the developer(s)
And yes...this is exactly how bots have already returned so quickly.
Valve pls fix

[Fireschlong #2Broke4MannUp]

Unless your favourite community server hasn't updated to the latest version, it doesn't really make sense to do that, aside from messing around in the previous version. The bots have returned because automated cheating is easy to implement, assuming that they had to tweak their software in the first place, not because they had access to 32-bit.

Still a fun thing to know IMO.

[Joey]

Originally posted by Fireschlong #2Broke4MannUp:

Unless your favourite community server hasn't updated to the latest version, it doesn't really make sense to do that, aside from messing around in the previous version. The bots have returned because automated cheating is easy to implement, assuming that they had to tweak their software in the first place.

Few bot hosters have already admitted they'd have given up once x64 was released due to how many things had changed and how little actual experience those people have. If anything x64 would've slowed them down tremendously, however the 32-bit version of the game is still accessible meaning they had very little to fix/maintain before coming right back up to speed. This thread is less self help for those looking to play on the x86 version but rather awareness as to why bots have returned so quickly.

[76561198329175320]

Originally posted by Joey:

Originally posted by Fireschlong #2Broke4MannUp:

Unless your favourite community server hasn't updated to the latest version, it doesn't really make sense to do that, aside from messing around in the previous version. The bots have returned because automated cheating is easy to implement, assuming that they had to tweak their software in the first place.

Few bot hosters have already admitted they'd have given up once x64 was released due to how many things had changed and how little actual experience those people have. If anything x64 would've slowed them down tremendously, however the 32-bit version of the game is still accessible meaning they had very little to fix/maintain before coming right back up to speed. This thread is less self help for those looking to play on the x86 version but rather awareness as to why bots have returned so quickly.

I am a bit confused. It looks like the 32-bit version is still accessible on Windows, yet on GNU/Linux it appears to be gone. Since bots run on GNU/Linux, it wouldn't make sense that they would still be able to access the 32-bit version of TF2, unless botting tools were to be ported to Windows.

TF2 Root Folder Screenshot:
https://steamcommunity.com/sharedfiles/filedetails/?id=3227261538

in tf.sh (the shell script that launches TF2) it appears that tf_linux64 is the only executable file it will launch on GNU/Linux.

Full shell script:
https://steamcommunity.com/sharedfiles/filedetails/?id=3228105432
The code that actually launches TF2:
https://steamcommunity.com/sharedfiles/filedetails/?id=3227252683

[Joey]

Originally posted by Ferris #KillWindows:

Originally posted by Joey:

Few bot hosters have already admitted they'd have given up once x64 was released due to how many things had changed and how little actual experience those people have. If anything x64 would've slowed them down tremendously, however the 32-bit version of the game is still accessible meaning they had very little to fix/maintain before coming right back up to speed. This thread is less self help for those looking to play on the x86 version but rather awareness as to why bots have returned so quickly.

I am a bit confused. It looks like the 32-bit version is still accessible on Windows, yet on GNU/Linux it appears to be gone. Since bots run on GNU/Linux, it wouldn't make sense that they would still be able to access the 32-bit version of TF2, unless botting tools were to be ported to Windows.

TF2 Root Folder Screenshot:
https://steamcommunity.com/sharedfiles/filedetails/?id=3227261538

in tf.sh (the shell script that launches TF2) it appears that tf_linux64 is the only executable file it will launch on GNU/Linux.

Full shell script:
https://steamcommunity.com/sharedfiles/filedetails/?id=3228105432
The code that actually launches TF2:
https://steamcommunity.com/sharedfiles/filedetails/?id=3227252683

If I'm not wrong I've seen others mention that you can do this on Arch.
I have no familiarity with linux outside of Parrot so others would need to chime in on this.

[waterflowfli]

Any way found on Macbooks yet?

[76561198326941277]

Originally posted by waterflowfli:

Any way found on Macbooks yet?

I have added you on a different account. I'd like to help you get this working.

[Argh!]

Originally posted by Joey:

Mind you this WILL NOT work if you're using Windows 7 as the parameter isn't recognized.

Er, this DOES work under my Windows 7 boot. It's exactly how I got it fully running there after the update.

For convenience, I also added that tf.exe to my Steam library as a non-Steam game, and added -steam to the Launch Options. Then prettied it up by renaming it to "Team Fortress 2 (32bit)", and added the official background/logo (from Steam\appcache\librarycache\) as custom images.

[Zaokllr]

Spend money on puter and not hat

[76561199510140356]

so if i'm using windows 7 i cant do ♥♥♥♥?

[Snake]

Originally posted by Ferris #KillWindows:

Originally posted by Joey:

Few bot hosters have already admitted they'd have given up once x64 was released due to how many things had changed and how little actual experience those people have. If anything x64 would've slowed them down tremendously, however the 32-bit version of the game is still accessible meaning they had very little to fix/maintain before coming right back up to speed. This thread is less self help for those looking to play on the x86 version but rather awareness as to why bots have returned so quickly.

I am a bit confused. It looks like the 32-bit version is still accessible on Windows, yet on GNU/Linux it appears to be gone. Since bots run on GNU/Linux, it wouldn't make sense that they would still be able to access the 32-bit version of TF2, unless botting tools were to be ported to Windows.

TF2 Root Folder Screenshot:
https://steamcommunity.com/sharedfiles/filedetails/?id=3227261538

in tf.sh (the shell script that launches TF2) it appears that tf_linux64 is the only executable file it will launch on GNU/Linux.

Full shell script:
https://steamcommunity.com/sharedfiles/filedetails/?id=3228105432
The code that actually launches TF2:
https://steamcommunity.com/sharedfiles/filedetails/?id=3227252683

Um hello? Virtual Machines?

[76561198329175320]

Originally posted by Aleigh Moané:

Originally posted by Ferris #KillWindows:

I am a bit confused. It looks like the 32-bit version is still accessible on Windows, yet on GNU/Linux it appears to be gone. Since bots run on GNU/Linux, it wouldn't make sense that they would still be able to access the 32-bit version of TF2, unless botting tools were to be ported to Windows.

TF2 Root Folder Screenshot:
https://steamcommunity.com/sharedfiles/filedetails/?id=3227261538

in tf.sh (the shell script that launches TF2) it appears that tf_linux64 is the only executable file it will launch on GNU/Linux.

Full shell script:
https://steamcommunity.com/sharedfiles/filedetails/?id=3228105432
The code that actually launches TF2:
https://steamcommunity.com/sharedfiles/filedetails/?id=3227252683

Um hello? Virtual Machines?

The virtual machines would have to run Windows, which the botting tools haven't been ported to at least to my understanding.