[GUIDE]Pserver - Server+Client setup

Discussion in 'Eve Online Accounts - Buy Sell Trade' started by EVE, 9/26/13.

Thread Status:
Not open for further replies.
  1. EVE

    Expand Collapse
    Bot Status (Automated): Handles automated general support inquiries

    0   0   0

    Likes Received:
    Yo, I luckily found a little guide for how to create an eve online pserver, so I decided to share it with you, credits go to '' EVEmulator '' Server Setup Quote: This is currently a very terse blurb about the steps needed to setup and run the server, feel free to expand and enhance this page. Server Build The first thing you will want to do is download the source code from sourceforge and build it. * * * L * For running a server, the only binary you are interested in is in the server/ directory. You may have to edit the main.cpp so that it can use your database (see the note under Database setup for more information). Go into the server directory and run a "make". This should result in a final executable named "eveserver", this is the server binary. You will need the mysql development resources installed (headers + libs). (The initial version may have some false dependancies on python development resources and libnet/libnids) NOTE: If you get link errors about libnet/libnids, go into the libs/ directory for each of those, and do a ./configure and then a make. Database Setup You will need to download and load up the eve database. Information is available in Data Files Create a directory named data under the root of the source tree, assuming you will run ./eveserver from the server/ directory. You need to obtain the strings.txt file from your eve client directory, under script/sys/ and put it into the data/ directory. If you cannot find this file or you do not have the client installed, you may find strings.txt at the page. Config File You will need to create a config file named evemuserver.xml in whatever directory you run the server from to tell the server how to connect to your database. You can also change your server's port, but I would not recommend changing it back to 26000... Code: An example file: eve
    eve eve Running it Once you have everything configured, you should be able to fire up the server. Do this by going into the server directory, and running ./eveserver You should see "TCP listener started." on success. Once you have the server running, you can try to log into it with your client. See the page for more information. Client setup Quote: Getting the EVE client to connect to a private server is relatively easy, what has been more difficult is getting it to never connect to the real servers for anything. Basically, when you start the client, it makes several connects to the live servers, and that is what we need to circumvent, otherwise they have a clear record in their log that your IP was connecting to a private server. The server currently works with client version 3913. You can find the correct client by asking google: . Please do not post direct links to the client from this site! Unfortunately, when CCP published 3913, they actually put out 3903, and then recalled it and put out 3913a. Another option is to grab EVE_3910.exe and then evepatch3910-3913.exe. This guide assumes you are running evemu on the same machine ( with the server on port 26001 and a web server listening on port 8000 (no web server is OK too). 1. Copy Client The first thing you should do when setting up to connect to evemu is to make a copy of your client. Just go into Program Files, find your EVE directory, and make a copy. Its a lot of disk space, but its better to not mess with your live playing environment. NOTE If you have just downloaded the client, please go directly to step 3, before trying step 2; you need to run the client at least once to get the materials required to perform step 2. 2. Edit prefs.ini Next, you need to go into the cache/ directory of your new copy of EVE, and open up prefs.ini. Find the line for the following values and change them: Code: advanced=1 debug=1 network=1 networkAdvanced=1 port=26001it is important to change the port, otherwise the client will call home for yet another patch check. 3. Script Mods Now you need to make a quick change to a python script to prevent the login screen from "calling home" asking for patch information, and other such activities... open up stdlib/lib2.py find 'def open', and replace the body (up through def install_opener, leave blank line) of that method with this: Code: def open(, data=None): global _opener rewrites = { '://eve-online' : '://', '://myeve.eve-online' : '://', 's://secure.eve-online' : '://', '://support.eve-online' : '://' } o = .get_full_() matched = False for k,v in rewrites.items(): if o[:len(k)] == k: new = v+o[len(k):] = Request(new, .get_data(), .get_headers()) matched = True if not matched: = None #prevent it from going anywhere we are not in control of if _opener is None: _opener = build_opener() return _opener.open(, data)4. Connect To Server Now your client is set up to not talk to the live servers. All you need to do is click in the server name field, and type in the IP address of your server ( and off you go. This should be all, trane.
Thread Status:
Not open for further replies.