Windows Server Installer :: Modular & Scripted

[c0ncrete]

1) it is a server emulator. private or pubic is entirely up to you.
2) you still have to have a WoW client to play on a WoW private server.
3) you have to change very little if you use one of the automated installers.
4) downloading game clients like WoW from randos off the 'net is how you get viruses.
5) EQ Titan is an emulated server, not a game client. Titanium is a client.

[Tegila]

You can host for yourself or publicly. The red error message was probably bc of being lan (mine always gives one while trying to connect to public login bc I turned it off) You do still have to have your own game, but titan is just fine. If it all installed as is, you just have to make the shortcut to eqgame and put in the relevant IP, then add patchme, plus put on relevant IP wherever else indicated on the page you got installer from. All this is explained in the links in the last page of posts here.

[Uleat]

wfmaacms-anl!

[Arkansas]

bump .....

[Inchronoth]

Hello Akkadius,

Installed into Windows 10 pc, and Windows 7 under vmware workstaion 14 on Windows 10 pc

Both installs with no error reported.

Had to fiddle with local login, but got installing and login finished within 10 mins!!

TY so much Akka!!!!

[GRUMPY]

No waves, no worries, just a warped sense of humour, haha.
You would need to edit the eqemu_config.json file in your server folder, wherever that was installed,
as well as the login.ini file. All references made to an IP, would have to be changed to local address,
(if you're running client on same box, locally) and a server login server was running.

[Uleat]

Go ahead and move the into its own thread, please.

I'll leave the current postings for now.

[Arkansas]

Quick question. Is the starting area in Gloomingdeep or however you say it or is it at the starting city's like the old days when your using EQ Tit. client ?

[Arkansas]

I think I see where the problem was actually. http://wiki.eqemulator.org/p?Akkas_P...ctions-windows
When it gets to where it says Your Good to go I stopped from there. I am guessing you have to continue on too the Local Lan part as well ? Because where it says good to go mine still connects to public servers. After following the steps. It put this ip
in 192.168.197.127 and I never changed it because it never said too until after the good to go part.. So I guess I should had just followed it through. My fault for thinking the good to go was meant that I was ready to connect :( So EQ Host file needs to say

[LoginServer]
Host=127.0.0.1:5999 (except 127.0.0.1 will be my IP ?)

instead of

[LoginServer]
Host=login.eqemulator.net:5998

[GRUMPY]

Might want to start asking questions here:

http://www.eqemulator.org/forums/forumdisplay.php?f=587

(this thread is only relevant to the "installer")

[Arkansas]

ok sorry guys. Thanks for all the help.

[Uleat]

Like GRUMPY said, no need to be sorry

You are more than welcome to ask any questions that you need to further your gaming experience here.

We just need to ensure the questions stay focused on the thread topic.

New problems really need to be started on their own thread due to relevance and focus. A post about a server crash from 8 years ago probably wouldn't be relevant today

[Arkansas]

k, thanks all for your help.

[Varrin1]

I used the akka install but when i go to start my server it says world.exe and zone.exe doesn't exist.. were those supposed to be created during the install?

Edit: Nvm I found the problem

[Bleuraiven]

I recently started this process and still have a long way to go. I was meandering through the process of getting things up, making alterations where necessary. Then, I hit the wall. No matter what I tried after reading through forum post after post, I couldnt seem to get the character to load. I was getting an error regarding the not able to connect to port 7000 from the client dbg.txt so I spent way too long trying to find out why the firewall settings that were clearly in place werent working. I finally decided I must have screwed something up royally and was in the process of rolling out 2 new virtual systems to attempt a clean install with server and client when I came across this...

Originally Posted by Laxative

I did a lot of testing and found the issue to be centered around login.ini

See at work I can end up on multiple subnets depending on where I jack in.

If my login.ini was specific.
W.X.Y.Z -- the client can only connect from W.X.Y.Z

If I get less specific: W.X.Y. (notice no entry in last octet)
Then clients can be anything from W.X.Y.1-254

So, we have a big network I just went with W. (no following octects) now I can connect from anywhere inside our internal network.

I was putting this together on a large private network as well and it was like WoW!, why didnt I think of trying that.

So big thanks to Laxative for the saving me from continuing to bang my head against a wall.

And mucho thanks to those who developed the tools, the scripts, and continue to assist those of us in need.