Semperverus

I'm struggling to get my old, previously working client from a year ago to properly connect to Hercules (all of the networking stuff is configured perfectly fine, correct packet version, etc.). I have an old client I had working before that refuses to log in because "Map does not exist". Loading from the .grf files directly server side does not work. I've tried rebuilding a client with the 2014-10-22b-RagexeRE client and the 2015-10-29a one. The client refuses to even connect to my server, even with the DNS diff patch. (Rejected with error number 22) On top of that, it seems that Hercules hates SystemD in Debian Testing. The login server and the character server seem to be silently crashing constantly, because sometimes I'll be refused at login, and other times I'll be refused after selecting the server name ("Hercules(0)"). They struggle even harder if you run athena-start start. I've had socket issues out the ass until I finally figured out that using the /imports/ folder doesn't actually function properly in this context. None of these issues were really a problem back before I had systemd. Pulling my hair out trying to juggle all of this. It seems absurd that there isn't an officially endorsed HerculesWS full client that's just pinned at the top and "guaranteed to work" with editing the clientinfo.xml and a patched and unpatched .exe pair sitting in the folder. Why does this have to be so incredibly difficult? (I've been at this for about a day and a half now)

Thanks. I got it working with either setting. I have a feeling though that changing it back to local host would prevent WAN connections.

So I have configured my server mostly properly, I think, so that my DNS converts to my current IP address (mydomain.com -> 123.456.789.000 for example), and I am successfully able to connect to my server over LAN, but as soon as I try to connect over an internet connection outside of my home, I can log into my account but after about 10 seconds it returns a "failed to connect to server" error. The login server recognizes my attempt, but as soon as it tries to pass me to the character server, it fails. Here is my network.conf configuration: / Network configuration file /* * List here any LAN subnets this server is in. * Example: * - char- (or map-) server's IP in LAN is 192.168.0.10 * - Public IP is 198.51.100.37 * If the list contains "192.168.0.10:255.255.255.0", any clients connecting * from the same 192.168.0.0/24 network will be presented with the LAN IP * (192.168.0.10) in the server list, rather than the public IP (198.51.100.37). */ lan_subnets: ( //"127.0.0.1:255.0.0.0", "192.168.1.151:255.255.255.0", ) /* * List here any IP ranges a char- or map-server can connect from. * A wildcard of "0.0.0.0:0.0.0.0" means that server connections are allowed * from ANY IP. (not recommended). */ allowed: ( "0.0.0.0:0.0.0.0", //"127.0.0.1:255.0.0.0", ) /* * List here any IP ranges a char- or map-server can connect from. These ranges * will also be excluded from the automatic ipban in casee of password failure. * Any entry present in this list is also automatically included in the * allowed IP list. * Note: This may be a security threat. Only edit this list if you know what * you are doing. */ trusted: ( "127.0.0.1:255.0.0.0", "192.168.1.151:255.255.255.0", ) where 192.168.1.151 is my Debian server's static LAN IP. should I be putting mydomain.com anywhere in here? and if so, how? EDIT: I figured it out everyone! For WHATEVER reason, there is nowhere in the documentation that states that the ports 6121 (character server) and 5121 (map server) need to be port forwarded in the router along with 6900. The way the documentation is written, it is made to sound that the map and character servers will connect to one another internally with these ports, and thus the only port you need open would be 6900, with all the traffic being piped through the login server. Let me tell you how many hours of sleep I've lost over this issue...

Hey kerbii, does this one function well for the 2014-10-22 client? Thank you

I mostly have my client and server pair set up and ready to go, but I'm getting a lot of issues with some maps being empty, some crashing on load, etc. This is due to the fact that I have the latest data.grf and rdata.grf. I have found a prontera.grf that works and prevents that map from crashing the client, but izlude is still pure black and you cannot move at all. The current main branch in the hercules github page has the client string set to 20141022, so that's the client I tried to get and would like to stick to until that string gets updated again (I consider it to be "latest stable"). I have the executable working and patched, but the 2016-1-13 (I think) data.grf and rdata.grf files. Any help would be appreciated!