TFS - backward protocol compatibility?

[czarnowidz]

Hi,

I am thinking about migrating from my custom server to the latest TFS. As a part of that, I would have to implement a capability to make TFS work with more than one protocol, depending on the configuration (I can run my current server on 7.72/8.6/8.72 protocols having same server). Wanted to ask about protocol compatibility rules for TFS official repository. Is there any restriction to keep only the latest (highest) protocol on the master? Or maybe such a feature (multi-protocol support) will be eligible to become part of TFS at some point?

I am aware that there are existing codes with downgraded protocol but I can see one major problem - all fixes and features from the TFS master must be applied manually.

 

[Ahilphino]

TFS devs has made the extremely dumb decision to only support newest Tibia protocols to the point where there's no compatible otclient for it anymore, not a single otclient works right now to connect to the server even though they tell us to use it in their readme. It's purely made for real tibia copies now. This has made it so theres no interest of anyone to use the distro, its pretty much dead and has no users anymore. Better use Tfs 1.1-1.2.
I think there are some forks that has downgraded it to 8.6, i do not think there is a multi protocol server.
In my best ur best effort is go tfs 1.1 / 1.2 and use otclientv8 to customize it to the client you want to use.

 

[Nekiro]

TFS devs has made the extremely dumb decision to only support newest Tibia protocols to the point where there's no compatible otclient for it anymore, not a single otclient works right now to connect to the server even though they tell us to use it in their readme. It's purely made for real tibia copies now. This has made it so theres no interest of anyone to use the distro, its pretty much dead and has no users anymore. Better use Tfs 1.1-1.2.
I think there are some forks that has downgraded it to 8.6, i do not think there is a multi protocol server.
In my best ur best effort is go tfs 1.1 / 1.2 and use otclientv8 to customize it to the client you want to use.

That's a false information
Mehahs otclient is compatible with latest tfs.

 

[Ahilphino]

That's a false information
Mehahs otclient is compatible with latest tfs.

OTClient log files points that does not understand many of the TFS messages - OTClient tells user to wait connection and log points many errors · Issue #4157 · otland/forgottenserver (https://github.com/otland/forgottenserver/issues/4157#issuecomment-1150686002)
Works great buddy!
I also doubt most people are interested in using mehah's otclient since it's still a buggy mess. The only option is to use real tibia client which I thought mark wanted to ditch 10 years ago already?

 

[Nekiro]

OTClient log files points that does not understand many of the TFS messages - OTClient tells user to wait connection and log points many errors · Issue #4157 · otland/forgottenserver (https://github.com/otland/forgottenserver/issues/4157#issuecomment-1150686002)
Works great buddy!
I also doubt most people are interested in using mehah's otclient since it's still a buggy mess. The only option is to use real tibia client which I thought mark wanted to ditch 10 years ago already?

I use it myself, so idk

 

[Gesior.pl]

Wanted to ask about protocol compatibility rules for TFS official repository.

Nobody will maintain more than one protocol. Protocols (tibia versions) are not compatible: different items, different spells, different damage calculation, different systems [item features, inbox in depot etc.].

(I can run my current server on 7.72/8.6/8.72 protocols having same server)

What about items? Spells? Map? 8.6 with 7.72 spells? 7.72 with 8.6 spells [what about missing animations in client]?
7.72 - 8.6 changes were nothing compared to 10.x - 12.x changes in protocol and features.

 

[czarnowidz]

Nobody will maintain more than one protocol. Protocols (tibia versions) are not compatible: different items, different spells, different damage calculation, different systems [item features, inbox in depot etc.].

Well.. There is a huge difference between providing a framework (that just handles the server stuff, like protocol, data management) and data pack (which is describing exactly the balance in game, calculations, monsters definitions). So far my understanding was that TFS is meant to be the a framework, not limited to a certain balance.

What about items? Spells? Map? 8.6 with 7.72 spells? 7.72 with 8.6 spells [what about missing animations in client]?
7.72 - 8.6 changes were nothing compared to 10.x - 12.x changes in protocol and features.

What about them? I can still keep the balance in the data packs (lua, xml, even config) without hardcoding stuff on the server side. For example there are mounts added between protocols 8.6 and 8.7, addons between 7.X and 8.X. Let's say I have 8.7 server that has implemented mounts system and addons. And yet there is no issue with running same data pack on 7.72 protocol - new features are just not transmitted to the client. Of course my data pack should be compatibile with the protocol because of the dat/spr differences. If otclient can handle the differences then the same stuff can be handled by the server.

Anyway, it was not my intention to start some kind of shitstorm here. Just a kindly question addressed to the TFS developers. If there is no intention to add such feature to the server - I understand and can live with this. But maybe it's something worth considering as a future milestone.

 

[Evil Puncker]

Just a kindly question addressed to the TFS developers. If there is no intention to add such feature to the server - I understand and can live with this. But maybe it's something worth considering as a future milestone.

there are no plans to work on it, it has been discussed internally (I was the one that suggested the idea back in the time), and while it's truly a nice idea and would bring more users to tfs, there is nobody willing to do it AND maintain it.

 

[zbizu]

There were multiple different market protocols since 10.98 (new description fields, added tiers, some bugfix, higher product prices). We'd need A LOT of ifs to keep multi protocol running.

Regarding tfs/otc compat: new features (most recently stat trackers) are being added creating new packet structures so it may break otc occasionally. We often avoid putting "if otclient" in tfs code in order to help otc devs discover issues with the protocol.

Keep in mind that there are at least three different version 12 engines, all with different features so there's still a lot of work to keep the client up with all of them. You can help the client grow by reporting packet issues whenever they are introduced with new server updates.

 

[Way20]

Server with multi-protocol from 7.4 to 11.x I think.

GitHub - Erza/optimized_forgottenserver

Contribute to Erza/optimized_forgottenserver development by creating an account on GitHub.

github.com