Should small client updates be disregarded by the OT community?

[Astrax]

Cip have been rolling update out way too frequently now, so frequently that it's impossible for us to keep up with it, and creates lots of confusion and useless tools.

The problem is as follows (just an example of what happens, disregard the numbers):
*Latest TFS 1.0 is for 10.35
*Latest RME is for 10.31
*Latest .otb editor is for 10.3
*Latest .dat editor is for 10.11
*Latest .spr editor is for 10.32
*Latest OT Client is for 10.31

And with the release of the 10.36 client yesterday....well, you get the glimpse of the problem.

IMO everyone should focus on a single version to keep this from happening, (I.E. 10.30 > 10.40 > 10.50 VS 10.30 > 10.31 > 10.32 > 10.35 > 10.36 > 10.xx). Most of these micro-updates are 99% useless to us anyways Thoughts?

 

[Cadyan]

My thoughts:
1) Stick with the new TFS and OTClient - and keep updating with every real Tibia update.
2) Players could have the option to "disregard" these new updates, with a simple "click" option.
3) Stop producing map trackers - or atleast stop releasing developed versions.

 

[Astrax]

My thoughts:
1) Stick with the new TFS and OTClient - and keep updating with every real Tibia update.
2) Players could have the option to "disregard" these new updates, with a simple "click" option.
3) Stop producing map trackers - or atleast stop releasing developed versions.

The frequently changing protocol version of the most popular server (TFS) is the main problem indeed. Currently, changing the protocol version in TFS requires source edits, and >90% of the people here don't even have an idea on how to do it (the greater the protocol change, the greater the complexity).
But even if you could change the server version with a click or simply editing config.lua, essential tools like the ones I listed would still be released for specific "micro" versions (.31, .32. .35). Without tools to facilitate making custom content, we encourage more of those bloody "DOWNLOAD & PLAY RL MAP SERVERS".

 

[Cadyan]

Ah, so what you are saying is that you would like to see some sort of global OT protocol, that doesn't necessarily need a protocol change, but rather just some of the updates.

So if we set TFS to 10.35, we wouldn't be changing the protocol ever again, but rather making the source edits work with 10.35 for all upcoming releases.

It alot to think about, alot to discuss. In the end, it's up to the programmers and what they think is best. I am simply here to make RPG's

 

[conde2]

Latest RME work on 10.36 since there is no change in Dat and Spr same for OTB editor and DAT editor, OTCLIENT and TFS walk togheter so it's only necessary update them when TFS is updated, the only problem I see is that they could be more dynamic / configurable with the protocol and reading Dat and Spr so them could be useful for more time

 

[Evil Puncker]

latest client version is always the best option, those who deny that are just lazy to learn how to update the necessary tools, that is my honest opinion

 

[Cornex]

latest client version is always the best option, those who deny that are just lazy to learn how to update the necessary tools, that is my honest opinion

Why? Those who wanna stick to older clients?

 

[Flatlander]

older clients only = less features.

In all honesty we should all be using OTClient.

 

[Hartass]

latest client version is always the best option, those who deny that are just lazy to learn how to update the necessary tools, that is my honest opinion

There are a lot of people actually downgrading their servers.

On topic:

I think there should be a general platform for all of the elements, from mapping to editing items, heck even a dat/spr editor that got updated the same time the client version updates.