SSCL Desert Storm back online!

[»LtNirvana]

UPDATE: Okay so the directory server issue is apparently not resolved. If you can't find the zone in the directory list just use the IP 69.164.209.244 and port 13000 to add the zone manually to your list while we try to sort out this nightmare.

 

DS is back online as SSCL Desert Storm.

 

The zone will be in a beta state for a few months while some things are improved and an ASSS conversion is started. The zone is playable and functional but the ship settings are subject to change as they have not been tested in more than 1v1 situations.

 

Graphics and SFX will be being improved and bot functionality will be improved as well during this beta period.

 

Thanks to everyone that made this reopening possible so far: L Y N X, Polix, and Chambahs for helping me with some business end problems and the server hosting by L Y N X. I'd also like to thank all the players who came back and let me know they would support the zone, as well as Cre and Dav1 for supporting this project.

 

Lt

Edited December 22, 2011 by LtNirvana

[»Maverick]

Congratulations on the reviving of the zone!

 

The reason why you're having an issue with the directory server is most likely because your zone isn't pingable (on normal port +1) to retrieve population numbers.

You can try it yourself at http://stats.sshq.net/dzone/3433/SSCL_Desert_Storm (click the http://stats.sshq.net/images/refresh.gif).

 

Check your firewall

Edited December 13, 2011 by Maverick

[»LtNirvana]

I'll let L Y N X know but I doubt that he would have a misconfigured firewall. Maybe he overlooked it though. Thanks bud.

[»Lynx]

Edit: Fixed! Thanks MMav! Edited December 13, 2011 by Lynx

[Dr Brain]

Change the port?

[»Lynx]

I couldn't change the DS port as Cheese used a password for DS originally - I think some of the other directory servers have a pretty long expiry time (mine is one day).

[»Maverick]

SSCL Desert Storm population statistics online:

 

http://stats.sshq.net/graphs/graph_87_1.png

[Dav]

win thanks mav

[»LtNirvana]

I changed the port of the zone to 13778 to try to resolve this directory server issue. Info on manually adding the zone updated on the original post.

 

Can anyone lend any advice on this? It's been like 2 weeks and I've tried everything. I've changed the name of the zone, the port, and the password in the directory section of server.ini and nothing will take. Absolutely nobody (including myself) can see the zone on the zone list when downloaded, despite all the directory servers being listed in the .ini.

 

The original problem seemed to stem from SSCL Desert Storm already existing on L Y N X's server by way of Cheese, so we thought it was a reclamation issue, but now I've change virtually every piece of info for the zone except the IP. WTF?

 

Lynx also checked his firewall, bear in mind that several zones are hosted on this server with no such issues.

 

LT

[Hakaku]

If you're using ASSS, have you at least made sure to load the directory module? It might be commented out in the modules.conf file.

[»LtNirvana]

Subgame on Wine

[»Maverick]

Have you tried changing the groupid, scoreid and/or ServerId?

[Resol]

Isn't that stuff for the biller..?

[»Maverick]

yes, but maybe it also affects the directory server.

 

Now if I think about it, "SSCL Desert Storm" was up and running in all the directory servers yesterday (or the day before that). Now you've changed the port and tried to have it register under the same name again in the same directory servers. It's quite logical the directory servers won't accept the change because they see as another server is trying to hijack the name. I guess you have to wait for the directory servers (mainly sscuservers.net) to drop the old Desert Storm name (and who knows how long that will take).

 

Why don't you use the port you had set previously?

[»Lynx]

When we used the original port, I believed it solved the issue on the majority of the directory servers. However, as there was a password used on the original (I believe a hash, which likely can't be re-generated) I think the remaining servers were disallowing the listing. This problem would probably be best resolved by going to the original port and simply waiting it out (I know it sucks, but hey, it's Subspace.)

 

Or use another zone name on another port.

[»LtNirvana]

My concern is that I used a different zone name and port and it did nothing.