*Unlock All Weapons* in server patch 1.02

[mofino]

Re: *Unlock All Weapons* in server patch 1.02

You 'da man, like Mofino. Thanks dude!

-mofino

[Bullitt]

Re: *Unlock All Weapons* in server patch 1.02

Hi, I went through this long thread, but didn't see an answer to this question:

Are global unlocks allowed on non-ranked servers? Does EA forbid this? Thanks!

Are they allowed? I believe so. Mine's been running this script (since October, 29, 2005) on my own webserver for months now. I just inserted the koolaidman's edit to the script. My server is still listed (unranked of course).

Its a beer and pretzels thing to have my clan and others to come in and try out the weapons before unlocking their ranked ones.

[PvtNoob]

Re: *Unlock All Weapons* in server patch 1.02

Hi Amd.Bullitt,

Not trying to be a to 'Noob' pain, but can you tell me how you setup the apache web server for BF2. I would really like to know how. I'm the type that needs step by step instructions. It seems nobody is willing to help on this subject.

My setup is the following

Machine 1 - connected to cable internet

Machine 2 - connected to machine 1 via Lan setup.

I am able to run the internet player to the 2nd machine via a port forwarding prog. That's no problem. The issue is running Apache on the 2nd machine in order to have unlocked weapons. I have not used Apache in about 2 yrs.I'm willing to learn the how to's on the full setup.

Thanks you for any help that you are willing to give.

PvtNoob

[PvtNoob]

Re: *Unlock All Weapons* in server patch 1.02

Hi,

Need some help on how to get unlocks. I know many here have it working. I've tried just about everything but no luck. I'm willing to listen if anyone has the time.

1. Tried the host file trick plus the editing of the serversettings file
Did not work
2. Tried setting up Apache2, edited the conf file, edited the host file
The end result was 403 error When trying to access the aspx file via the browser. Basically, I did not have permission. Tried editing the conf file in Apache and added the ExecCGI. Got an internal server error.
3. Also, added the .htaccess file with the AddType application/x-httpd-cgi .aspx to the ASP directory in Apache.

Kind of stuck. Any help is appreciated.

I'm using the 1.12 patch.
Thanks
PvtNoob

[geddeth]

Re: *Unlock All Weapons* in server patch 1.02

Kind of stuck. Any help is appreciated.

Which platform are you setting up Apache on? Did you check the log for what caused the internal server error? Did you check the path to the perl interpreter in the first line of the script? Did you install Perl?

[Bullitt]

Re: *Unlock All Weapons* in server patch 1.02

Hi Amd.Bullitt,

Not trying to be a to 'Noob' pain, but can you tell me how you setup the apache web server for BF2. I would really like to know how. I'm the type that needs step by step instructions. It seems nobody is willing to help on this subject.

My setup is the following

Machine 1 - connected to cable internet

Machine 2 - connected to machine 1 via Lan setup.

I am able to run the internet player to the 2nd machine via a port forwarding prog. That's no problem. The issue is running Apache on the 2nd machine in order to have unlocked weapons. I have not used Apache in about 2 yrs.I'm willing to learn the how to's on the full setup.

Thanks you for any help that you are willing to give.

PvtNoob

I'm using apache v1.3.

Letsee, I followed the guide to the letter here. Install Apache, adjust MIME setting for the script, change hosts file to point to localhost, install script, fire and forget. Oh I already have perl installed, perhaps thats where its screwing up for you? EDIT: I already have a working Apache server set up. Can you go to http://yourservermachine's-IP-address and get the default apache placeholder page?

Here is the guide I used _to the letter_

http://www.totalbf2.com/forums/showp...41&postcount=1

change your mime type
http://www.totalbf2.com/forums/showp...26&postcount=8

Kidman's SF mod to the original script (unlocked 1.12 weaps)
http://www.totalbf2.com/forums/showp...11&postcount=6

Thats ALL I used. Remember to change your hosts file on THE SERVER MACHINE ONLY for this to work.

[geddeth]

Re: *Unlock All Weapons* in server patch 1.02

Ugh .. I'm having trouble too. I set the servers sv.internet variable to 1, enable global ranks and global unlocks and start the server from command-line, but when a client joins, it says the server does not have global unlocks enabled. And they're not enabled in the game.

I think this might be related to the clients using only offline accounts. Anyone have experience with this tweak and offline accounts?

[Bullitt]

Re: *Unlock All Weapons* in server patch 1.02

Ugh .. I'm having trouble too. I set the servers sv.internet variable to 1, enable global ranks and global unlocks and start the server from command-line, but when a client joins, it says the server does not have global unlocks enabled. And they're not enabled in the game.

I think this might be related to the clients using only offline accounts. Anyone have experience with this tweak and offline accounts?

Its not going to work for offline accounts. Online only. It has to query the gamespy servers (or your http server emulating those servers) for the tweak/mod/whatever to work properly.

[PvtNoob]

Re: *Unlock All Weapons* in server patch 1.02

amd.Bullitt,

I finally got my Apache server to run the getunlocksinfo.aspx file. I had to re-edit the apach conf file. Now, I have to point my bf2 game server to my webserver. I guess I need a little help there, too. Can you supply the answer to that one or perhaps a link? Btw, I did a search on the net and found a great link for apache webservers running perl on a windows system. The first line of the aspx file would not allow me to run it:

#!/usr/bin/perl ....... I had to modify that line to #!/X:/www/perl/bin/perl.exe in order to run on a windows xp system.

Thank you for your help!

pvtnoob

[geddeth]

Re: *Unlock All Weapons* in server patch 1.02

PvtNoob, that would be the hosts file trick. On your BF2 server, edit the hosts file to point the gamespy server domain name to your webserver. It's mentioned elsewhere in this thread (I think Bullit's first link above has the info).

[geddeth]

Re: *Unlock All Weapons* in server patch 1.02

Its not going to work for offline accounts. Online only. It has to query the gamespy servers (or your http server emulating those servers) for the tweak/mod/whatever to work properly.

Hmm ... I was afraid of that. But the BF2 server doesn't know if the clients are offline or online in advance .. so when does the server actually do the querying to gamespy? On the first client connection? And how does this explain the fact that the global unlocks setting does not have any effect - could this be because there is no internet connection? (well there is, but almost all non-port 80 traffic is blocked).

[IndianScout]

Re: *Unlock All Weapons* in server patch 1.02

Always an A$$HAT trolling around to put some bad info in the mix.


The EULA from EA does not cover this type of situation, I had it reviewed by our corp Atty. The conclusion: If you do not modify any game content, you are safe.


EA cannot tell me how to administrate my HOSTS file, nor can they effect anything I want to do with the DNS services on my machines.


I'd suggest you take your troll'n a$$ elsewhere and bump your post count there.


Also try READING the eula instead of skipping it....yeah we know it's hard without DR. Suesse attached to the title, but drag that public school education up and give it a shot.



Munson

maybe your so called corp attny should read this..

EA/DICE/PB have been aware of this since before this thread started...

1. GLOBALLY ENFORCED RANKED SERVER RULES
These are rules that all admins/players using ranked servers are expected to observe and are set by EA under the EULA.
a. You may not arrange for the exchange or transfer of any pirated software or other contraband while you are on our servers or these Services, this will lead to immediate ban.
b. You may not market, promote or advertise anything, or make any other form of solicitation (including pyramid schemes and chain letters) on any of our services. Clan recruiting is not prohibited.
c. You may not change (hack) any core game files or employ external programs or cheats for the purposes of giving yourself an unfair advantage over other players.
d. Server admins may not change any game settings defined as standard for ranked servers (ticket ratios, server password, round time, etc.)
e. Server admins may not explicitly or implicitly (by actions) enforce restrictions on vehicles or weapons that players can use while on your server (e.g. knives only, aircraft prohibited except for clan members, etc.)
f. Server admins may not explicitly or implicitly (by actions) enforce restrictions on roles or kits that players can use while on your server e.g. Commander, Squad Leader, Spec Ops, etc.)
g. Server admins may not use non-standard maps or modified versions of standard maps.
h. Players may not use or exploit game mechanisms to artificially boost their scores ("stats padding") and Server admins may not knowingly allow or encourage this activity on their servers.
i. Players may not Impersonate EA ADMINS.

[geddeth]

Re: *Unlock All Weapons* in server patch 1.02

What's your point, Indian? Have you understood what this thread is about?

Let me sum it up: this change affects the entire unranked server, not any individual player.

Clear enough?

[IndianScout]

Re: *Unlock All Weapons* in server patch 1.02

I wasnt responding to whether this applied to ranked/unranked servers

I was replying to his particular post...

no harm no foul...


:)

[Bullitt]

Re: *Unlock All Weapons* in server patch 1.02

amd.Bullitt,

I finally got my Apache server to run the getunlocksinfo.aspx file. I had to re-edit the apach conf file. Now, I have to point my bf2 game server to my webserver. I guess I need a little help there, too. Can you supply the answer to that one or perhaps a link?

pvtnoob

Anyway on to the fix.

For Linux servers:
1. edit /etc/hosts and add this line:

209.91.168.238 bf2web.gamespy.com

2. enjoy!

For Windows servers:
1. edit X:\$WINDOWS\system32\drivers\etc\hosts and add this line:

209.91.168.238 bf2web.gamespy.com

2. enjoy!

Basically I'm emulating the "unlocked weapons" responses from Gaymenspy.

This is not a flame :)
Lemme break it down in conceptual terms. Mofino used a packet sniffer to figure out what was being passed. He then made a simple perl script to emulate that response. Using a webserver he can now properly pass the data back to a client (the BF2 server). Now the only thing that needs done is to "Trick" your Bf2 server into looking at a specific server instead of the normal Gamespy server. This is done via the hosts file. The server will now think that your server is the "Official" gamespy server using a DNS trick thats as older than the DNS system.

Instead of using the above IP addresses in your hosts file, you will need to insert the IP of YOUR webserver running the apache/perl script.

Mine looks like this:
/etc/hosts

127.0.0.1       bf2web.gamespy.com

Since you are running windows, find the IP address of your server (ipconfig from the server) and go into your SERVER's Windows\system32\drivers\etc folder, edit the hosts file in notepad and put your apache server's IP address <tab> bf2web.gamespy.com and save the file (be SURE it does NOT put a .TXT extension on it).

Fire up the apache, fire up the server, and join your server and voila!

Edit: This modification is to be done on THE SERVER ONLY.

edit #2 if it doesnt work, reboot the server. If it still doesnt work, make sure that you are allowing apache to listen on the appropriate interface

The httpd.conf file

# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, in addition to the default. See also the <VirtualHost>
# directive.
#  
#Listen 3000
#Listen 12.34.56.78:80

#  
# BindAddress: You can support virtual hosts with this option. This directive
# is used to tell the server which IP address to listen to. It can either
# contain "*", an IP address, or a fully qualified Internet domain name.
# See also the <VirtualHost> and Listen directives.
# 
#BindAddress *

Listen should be set to your IP address or commented out (# on the line)
BindAddress should be * or commented out.