[Development] MachineManager

[blapanda]

Anyone figured out some offsets regarding to "running it multiple times without checking pre-existing instances on the same machine"? (""Multiclienting"")

TL;DR

Some info as it looking right now.

[Syloxx]

mean something like this?

[blapanda]

Originally Posted by Syloxx

mean something like this?

That is a multi shard-/gameserver, what you are trying there. It is a split-server hosting.

Mine is a multi hosted server cluster, tried to be hosted on the same hosting-machine.

Works as
Hosting-Machine + VM
or
Hosting-Machine-No1 + Hosting-Machine-No2
but not as
Hosting-Machine only.

[Royalblade*]

Panda the way you explain it is just to confuse people by using more fancy words..

So you want to host multiple servers or rather shards on the same machine?

It's pretty simple once you know how the cert works. Other than that you need to force ips (multiple apps available there..).

And you need to to replace a JNZ to a JMP to get rid of the "semaphore already exists" error message. Then you can easily start up the same module twice.

It's simple. Startup a module, start another one with olly. Put a BP when you get that ****** popup window. Trace back from there to where its being called from. Scroll up a bit, the first JNZ you find will be the check for an existing instance running.

PS: We did something similar last year, if i remember correctly the above explanation should be at least very close.. so even if you dont know any asm, you should be able to easily find it.

Oh and just so ya know, sro files aren't performant when you run the same instance on the same host. Nor is there a playerbase for it.

Also, you need ONE machinemgr only, dont see a reason why you've got two in your list there.

PS: Don't forget that both of those shard/gs/agents need to run on different IPs.

Yes 127.0.0.1 will be a *****, don't recommend it.

[blapanda]

Originally Posted by Royalblade*

Panda the way you explain it is just to confuse people by using more fancy words..

So you want to host multiple servers or rather shards on the same machine?

It's pretty simple once you know how the cert works. Other than that you need to force ips (multiple apps available there..).

And you need to to replace a JNZ to a JMP to get rid of the "semaphore already exists" error message. Then you can easily start up the same module twice.

It's simple. Startup a module, start another one with olly. Put a BP when you get that shitty popup window. Trace back from there to where its being called from. Scroll up a bit, the first JNZ you find will be the check for an existing instance running.

PS: We did something similar last year, if i remember correctly the above explanation should be at least very close.. so even if you dont know any asm, you should be able to easily find it.

Oh and just so ya know, sro files aren't performant when you run the same instance on the same host. Nor is there a playerbase for it.

Also, you need ONE machinemgr only, dont see a reason why you've got two in your list there.

PS: Don't forget that both of those shard/gs/agents need to run on different IPs.

Yes 127.0.0.1 will be a bitch, don't recommend it.

Take a short look about these pictures:

 Spoiler

I had that already, hosting multi-shard/gameservers at once. Splitting the regions into 1 and 2 and even 3. That is not my aim for this case.
This one here is for multiple servers with their respective databases, rates, etc.

I am able to host 2 servers, ONLY if they are split to Machine1 and Machine2 (Machine2 is in this case a VM).

This cluster should aim to be ran on a single Machine, without any additional soft-/hardware (ergo, e.g. laptop or virtualboxes).

With the current MachineManager, no one is able to host multiple instances with it on the same hosting machine. I am not able to hook up the machinemanager.exe in my ollydbg, since it won't show anything. agentserver.exe, sr_shardmanager.exe and sr_gameserver.exe are working fine.

Edit: Nvm. Just did something pretty rationally to make it actually work on the main machine.
Can be closed.

[Nectix]

#closed