The Mana World Forums

visaboy wrote:Was was support removed from the project to begin with?
Is it no longer being developed?

The reason is that ManaServ is not a stable target, so it was disabled for the stable client release.

o11c wrote:

visaboy wrote:Was was support removed from the project to begin with?
Is it no longer being developed?

The reason is that ManaServ is not a stable target, so it was disabled for the stable client release.

Alright, so to clear things up.

What is the project currently in active development? tmw or mana?

It makes no sense to disable manaserv if that's the active project.

visaboy wrote:

o11c wrote:

visaboy wrote:Was was support removed from the project to begin with?
Is it no longer being developed?

The reason is that ManaServ is not a stable target, so it was disabled for the stable client release.

Alright, so to clear things up.

What is the project currently in active development? tmw or mana?

It makes no sense to disable manaserv if that's the active project.

Well ManaServ has currently only one active gameserver. This is invertika. But invertika uses an outdated server so the current client is incompatible with it. Currently there were heavy modifications on manaserv which made it unsusable (currently fight and skill system is a bit broken). So the idea was to prevent confusion about not working ManaServ. But i guess in 0.7 it will be probably possible to enable ManaServ support again.

Well back to your question:

ManaServ is still in active development but is (as i said) currently not really usuable.
TMW uses eAthena which is stable since while but does not have all the features desired. Best ask o11c about development of eAthena.

Best regards
Ablu

Just to clear some things up:
Bertrams example has an small issue:
He binds the game and chat server to internal ips: This won't work for public servers because this ip will be sent to the client and the client will try to connect to that ip.
Well of course that wont work if the client is not in the same network like the server. So you would need to set it to your public ip. But when you are behind a router you do not know this ip and your machine cannot bind anything to it. This issue is fixed now:
You can now define two further configuration values: This is now the ip or domain that is sent to the client. When this option is not set the net_chatHost or net_gameHost will be sent.

So you need to put there your public ip of your router (or domain) and configure your router to do the port forwarding to the right machine in the local network.

Best regards,
Ablu