• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

OTClient Multi world system otcv8

bpm91

Advanced OT User
Joined
May 23, 2019
Messages
1,046
Solutions
7
Reaction score
180
Location
Brazil
YouTube
caruniawikibr
I would like to know if anyone can say, let's say I put a multiple worlds system on my website system, for example so players can log into the same account in several different worlds, just like Tibia. What should I do on the client, for example, so it can accept these worlds? let's say 1 world and database per computer.

Tfs 1.5 otcv8 7.72
 
I would like to know if anyone can say, let's say I put a multiple worlds system on my website system, for example so players can log into the same account in several different worlds, just like Tibia. What should I do on the client, for example, so it can accept these worlds? let's say 1 world and database per computer.

Tfs 1.5 otcv8 7.72
There is no TFS 1.5.
There also is not a TFS that uses client protocol 7.72.

If you want help, you should make sure to provide accurate information to the ones you are trying to get to help you.
 
Nekiro downgrade for 7.72 is what you are using and what you should have said, as that is the specific version of code you are using, I would even recommend linking to the repository you are using when telling others your version.

TFS 1.5 is mentioned because its what codebase was used to make it from, but 1.5 only existed while it was being made, its a development version, it doesn't actually exist. There is 1.4, and 1.6, but no 1.5. Just like right now, the development that is going on is called 1.7 if you refer to that codebase, but there is no official 1.7 and never will be.

At any rate, there is no multi-world that is known to be completely compatible with the code you using. All of them will require knowledge and expert editing to make work, also... they are all old and scattered on this forum or on github. What you are asking for help with is no simple task by any means, you will want to learn as much as you can to achieve it, or be prepared to let your wallet suffer.
 
I didn't understand anything you said, but I downloaded it while it was version 1.5, and the posts that people make are 1.5, so if you want to know if I used it after the update or before, then it's 1.5 too.
 
Okay, I just want to know if when I implement a multi world system in a myaac for example, if I should change it in tfs and in the client or just in the client, because I don't have this function yet. So I'll have to hire someone to do it.
 
You will just want to make a special login server is all. This login server connects to the database, finds the world id, and connects to the appropriate server based on that, is how its most commonly done I believe.
 
So you would only have to configure the website, but otv8 doesn't change anything? Clause that I have 3 machines each one has an IP and a database, in otcv8 would I edit the 3 IPs? or 1 ip? I do not understand
 
In the client you would logon to the login server... it would decide where to pass the connection after you have chosen your character, based on what world that character is in... so the only thing you would need is someone who can setup the mysql and website parts, and someone who can make for you the special login server.
 
It usually works this way:
1. A login server (or website acting like one) that pulls characters from several databases per account
2. Client connects to login server and receives all characters with their world info, ip etc, then just sends to protocolgame to login
3. Account maker is creating account in account table of login server

Making acc maker support several worlds is probably way more work than setting up subdomain per every world, because it has to query two different databases.

I also saw multi world systems where people added world_id to every table in database and just use one for both servers, I wouldn't recommend that for several reasons.

It's usually a lot of work to get this done and nowhere easy.
 
Last edited:
Back
Top