Crossfire Forum

It would be likely then that your reversion corresponded to the eventual timing out of sombe of those damn ben's noodle entries, bringing it below the crash threshold.

Perhaps you can implement a one-server-one-listing technology? Then there'd be one damned bensnoodle.idiot.no-ip.com.

There is, each Ip adress is only listed once, no the way to fix the problem is to force the hostname to be something that resolves to the ip adress, then when bens-bloody-noodle starts occupying half of a class b subnet, the old adresses will no longer resolve to the correct ip and be thrown out. (and at this point, if it takes the real one with it then so much the better from my POV)

There should be a limiter that allows only _4_ different ip server with the same address.

do you mean the same hostname?

at the moment there is only one server with any given adress.

Yes. So if someone does steal metalforges name, you still have another metalforge to goto, because only 4 can have the name metalforge.

That means you need only 4 systems and you can lock out metalforge completely....

Well, having an infinite amt of systems makes it impossible to even find the real metalforge.
Should there be an approved server list? Where the new servers send a notification to a person, who then either gives it a go (adds into to the meta servetr list) or rejects it (doesn't put it in)?

What if the metaserver was to try and connect to each server on the list every half-hour or so? If it didn't send a response that was like that of a crossfire server, then it would be removed from the list.

Objection to this: It will cause some 'dwarf left the game' messages at frequent intervals. (maybe alter the leaving notification function to not print that if the host is the same as the metaserver?)

But bensnoodle crashed every 10-20 mins I thought. Surely we can set it to more like 5 mins, because multiple server names is quite a handful to sort though.