[Release]9.4 Official Files

ThunderNikk · 10/26/2017, 22:31

Quote:

Originally Posted by Ghost Informatics

There's a bug with the decompose if you use it use it on your own , it's cause a dc problem to the herlock .

In older epics that was caused by missing drop group entries in the decompose resource table.

InkDevil · 10/26/2017, 23:55

Quote:

Originally Posted by SilentWisdom

From what I understand in older epics collision detection was handled solely by the client for monsters/players etc.. but in newer epics the server also plays a part. This is likely the cause of Game content::IsBlocked

I thought something equal.
My experience told me most of these blocked contents are tries of (for example) monsterspawns in non-enterable area.
Coordinates where it tried to spawn are the numbers which are included in its message.

asddom · 10/27/2017, 13:32

guys i got problem ... when i use the hamachi IP in the GS and login to the game it's shows me a message with strange language and (10060) .. so what to do ?

if i use 127.0.0.1 ip it works fine

ThunderNikk · 10/27/2017, 15:05

Use the string resource in the SQL for your launch language. There are multiple ones already available in the files.

That pretty much should be a "can not connect to log in server" message so make sure your ports (all but 1433) are forwarded through your router and modem.

~~thund22222~~ · 10/27/2017, 15:16

@

thanks so much for this file, but how can i use ServerLauncher?
i should use some tool & .exe launcher right?

Ghost Informatics · 10/27/2017, 15:38

Quote:

Originally Posted by thund22222

@Ghost Informatics
thanks so much for this file, but how can i use ServerLauncher?
i should use some tool & .exe launcher right?

The server launcher is not the patch bin if you mean to use the official launcher .. the server launcher is bin to auto restart the GS&the auth by using this commands,

start_auto_launch --> This command to auto start the GS & Auth if they down .
stop_auto_launch --> This command to stop the auto launch .

You can edit the serverlauncher.opt and put any bin you want to auto start not only the GS & Auth .

smoegsmoeg · 10/27/2017, 18:09

ok - please call me names but:
WT actual F....
It should all work BUT.. I still have this issue - I can't connect.... (Server runs in Vbox instance....) - the port wont open....

attached are netstat from server and pic of my auth and cmd....
why is the port not open.... what do I miss?

Help me EPvP, you're my only hope...

Spoiler

ThunderNikk · 10/27/2017, 18:39

Did you configure it in Windows advanced firewall?

Is something else using the same port?

smoegsmoeg · 10/27/2017, 18:45

Quote:

Originally Posted by ThunderNikk

Did you configure it in Windows advanced firewall?

Is something else using the same port?

firewall is off (domain, home and public) deactivated the service.
and no, and if so it would have been seen in netstat -a

i just don't get it...

all looks fine

Ghost Informatics · 10/27/2017, 19:10

Active the fire wall then allow to the ports in the fire wall TCP+UDP it will work .

smoegsmoeg · 10/27/2017, 19:22

Quote:

Originally Posted by Ghost Informatics

Active the fire wall then allow to the ports in the fire wall TCP+UDP it will work .

doesn't make sense - when the service is deactivated - everything goes. the fact that netstat does not find an listening port means auth is doing something else.
at the moment I'm copying over a fresh 2012r2 with sql14 vm and will try from scratch. *headscratcher*

Ghost Informatics · 10/27/2017, 19:39

Quote:

Originally Posted by smoegsmoeg

doesn't make sense - when the service is deactivated - everything goes. the fact that netstat does not find an listening port means auth is doing something else.
at the moment I'm copying over a fresh 2012r2 with sql14 vm and will try from scratch. *headscratcher*

Your problem with the fire wall ... try as i said

smoegsmoeg · 10/27/2017, 19:57

Quote:

Originally Posted by Ghost Informatics

Your problem with the fire wall ... try as i said

didnt mean to offend, but, what isn't there can't block, either way - I did try it - still no open port in netstat -a (netstat would show the listening port even if the Firewall would block it) and client now runs into 60sec timeout instead of quitting directly with "can not connect to login server"
pelz3/12 is 9881 udp/tcp allowed separately

ThunderNikk · 10/27/2017, 20:15

Is it listed in your auth.opt?

smoegsmoeg · 10/27/2017, 20:17

Quote:

Originally Posted by ThunderNikk

Is it listed in your auth.opt?

yes (see my older post

Spoiler

) io.auth.port:9881