Old Version of TFS

StreamSide

Joseluis Gonzalez
Joined
Aug 31, 2007
Messages
3,082
Best answers
18
Likes
685
Location
Arica - Chile
#1
Nowadays there is a lot of people looking for the perfect and full datapack to make their projects, also there is a lot of people looking for older versions of current Tibia so here is my question.
Is there anyone who is interested in replicate some old features in the current TFS version?
I can downgrade the sources but I'm lack of information about the gameplay of those years._
Maybe there is some datapacks already working with those features but I do not care, I always wanted to do something by myself and I guess that I did it, but some help might be appreciated.

Thanks for reading. Love you all.

//edit
Some things are going to be added like item height stuff and uh trap, like the only 2 things that I remember lmao.
Also thanks @Ninja for always being there to help, I owe you some fries.
 
Last edited:

Ahilphino

Well-Known Member
Joined
Jun 5, 2013
Messages
1,243
Best answers
0
Likes
335
#3
tfs 1.3 in lower protocols would be very nice! theres ninjas 8.6 and printers 8.0 versions but i think they are both bugged
and also add back animatedtext functions
 

StreamSide

Joseluis Gonzalez
Joined
Aug 31, 2007
Messages
3,082
Best answers
18
Likes
685
Location
Arica - Chile
#4
does your server contain any sources ?
yeah, its open source as TFS, wanna contribute?

tfs 1.3 in lower protocols would be very nice! theres ninjas 8.6 and printers 8.0 versions but i think they are both bugged
and also add back animatedtext functions
I used ninja's version as guide, and I will add that feature for sure :D
Do you remember anything else?
 

Ahilphino

Well-Known Member
Joined
Jun 5, 2013
Messages
1,243
Best answers
0
Likes
335
#7
its good
but did you downgrade from ninjas 8.6 version or from the actual current tfs version?

i think downgradeed from current tfs would be best
and if you can add all oldschool features it would probably be biggest oldschool distro
but theres much stuff that i dont remember, probably @Peonso is best guy to help with those things
u could also take spell formulas and other thinks from othire, i think thats the most accurate oldschool server
 

StreamSide

Joseluis Gonzalez
Joined
Aug 31, 2007
Messages
3,082
Best answers
18
Likes
685
Location
Arica - Chile
#8
its good
but did you downgrade from ninjas 8.6 version or from the actual current tfs version?

i think downgradeed from current tfs would be best
and if you can add all oldschool features it would probably be biggest oldschool distro
but theres much stuff that i dont remember, probably @Peonso is best guy to help with those things
u could also take spell formulas and other thinks from othire, i think thats the most accurate oldschool server
Current tfs (1.3 I guess), latest features here, like xtea changes and rsa key as file
 

Peonso

Godly Member
Joined
Jan 14, 2008
Messages
1,456
Best answers
22
Likes
928
#9
You have some info here Game mechanics through time. (https://otland.net/threads/game-mechanics-through-time.216072/) Best tip I can give is to go through all OTHire commits to see if them apply. There are many details in OTHire that people doesn't even consider exists. Like monsters spells interval, changing target strategies, fleeing algorithms, spells exhaustion, spell formulas, accurate shielding mechanic, acurate shielding and armor for monsters. You might have to fix shotting runes in invisible monsters, stairhop delay, parcel block, uh trap, rope script. Here you can get some old spell scripts (they have a workaround to shot invisible monsters) though formulas are not perfect and monsters peonso/tfs1041_oldschool (https://github.com/peonso/tfs1041_oldschool/tree/master/server/data/monster). Also check what have been done here: mattyx14/theforgottenserver-7.4 (https://github.com/mattyx14/theforgottenserver-7.4/commits/master) <- this is @ond downgrade

Also what client is that? 7.72 with 7.4 dat+spr?
 
Last edited:

StreamSide

Joseluis Gonzalez
Joined
Aug 31, 2007
Messages
3,082
Best answers
18
Likes
685
Location
Arica - Chile
#10
You have some info here Game mechanics through time. (https://otland.net/threads/game-mechanics-through-time.216072/) Best tip I can give is to go through all OTHire commits to see if them apply. There are many details in OTHire that people doesn't even consider exists. Like monsters spells interval, changing target strategies, fleeing algorithms, spells exhaustion, spell formulas, accurate shielding mechanic, acurate shielding and armor for monsters. You might have to fix shotting runes in invisible monsters, stairhop delay, parcel block, uh trap, rope script. Here you can get some old spell scripts (they have a workaround to shot invisible monsters) though formulas are not perfect and monsters peonso/tfs1041_oldschool (https://github.com/peonso/tfs1041_oldschool/tree/master/server/data/monster). Also check what have been done here: mattyx14/theforgottenserver-7.4 (https://github.com/mattyx14/theforgottenserver-7.4/commits/master)
Thanks for this, specially for this one:
Like monsters spells interval, changing target strategies, fleeing algorithms, spell formulas, accurate shielding mechanic, acurate shielding and armor for monsters. You might have to fix shotting runes in invisible monsters, stairhop delay, parcel block, uh trap, rope script.
Those are good issues to work on it, did you use discord?
 
Joined
Feb 15, 2014
Messages
303
Best answers
0
Likes
5
#12
if the server will be 7.4 version i have alot of information about the gameplay of those years, you can add me on discord Jhon#0029
 

StreamSide

Joseluis Gonzalez
Joined
Aug 31, 2007
Messages
3,082
Best answers
18
Likes
685
Location
Arica - Chile
#14

Don Daniello

/root
Staff member
Administrator
Joined
Apr 11, 2008
Messages
3,421
Best answers
12
Likes
738
Location
Proland
#15
A very important or useful practice in the case of downgrading TFS is to keep good commit history in git, so that when the upstream TFS repo gets new commits, you are able to rebase on top of that with little to no effort.

The main issue with current downgraded versions of TFS is that they are never updated and forgotten (more than forgottenserver!). You can't trust those and you don't even know what version they come from.

Hence, I would suggest making edits and commenting exactly (in the commit message) what is it you're changing and keeping them organized and small. That makes it easier to understand what may need to be redone when it can't be automatically rebased on top of a new version.

There are many details in OTHire that people doesn't even consider exists. Like monsters spells interval, changing target strategies, fleeing algorithms, spells exhaustion, spell formulas, accurate shielding mechanic, acurate shielding and armor for monsters. You might have to fix shotting runes in invisible monsters, stairhop delay, parcel block, uh trap, rope script.
Ideally, the patches/commits would be separated into two categories:
  • Necessary: meaning, they are changes to the protocol/game required to log in with particular older client for it not to crash
  • Other: like the different formulas, exhaustion, algorithms, targeting, etc.
    Those make the game look like the older version but they are not strictly required to be able to connect.
If you do that, you can be sure that it will be easy to update in future. Keep in mind that you can update (amend) your commits.

And just for comparison, these are bad commit messages:
1546993547076.png

And these are good commit messages:
1546993578968.png

Obviously the goal is to make good commit messages. That helps a lot later on.
 

StreamSide

Joseluis Gonzalez
Joined
Aug 31, 2007
Messages
3,082
Best answers
18
Likes
685
Location
Arica - Chile
#16
A very important or useful practice in the case of downgrading TFS is to keep good commit history in git, so that when the upstream TFS repo gets new commits, you are able to rebase on top of that with little to no effort.

The main issue with current downgraded versions of TFS is that they are never updated and forgotten (more than forgottenserver!). You can't trust those and you don't even know what version they come from.

Hence, I would suggest making edits and commenting exactly (in the commit message) what is it you're changing and keeping them organized and small. That makes it easier to understand what may need to be redone when it can't be automatically rebased on top of a new version.


Ideally, the patches/commits would be separated into two categories:
  • Necessary: meaning, they are changes to the protocol/game required to log in with particular older client for it not to crash
  • Other: like the different formulas, exhaustion, algorithms, targeting, etc.
    Those make the game look like the older version but they are not strictly required to be able to connect.
If you do that, you can be sure that it will be easy to update in future. Keep in mind that you can update (amend) your commits.

And just for comparison, these are bad commit messages:
View attachment 33794

And these are good commit messages:
View attachment 33795

Obviously the goal is to make good commit messages. That helps a lot later on.
Thats the main reason I wanted to do the first part by myself, cus I didnt knew correctly what I was doing, also your commits are related to some fixes/changes, mine are related to the first part of the downgrade, and just -fyi- I didnt wanted to create compatibility on all versions, just wanted to test myself doing the downgrade.
 

Don Daniello

/root
Staff member
Administrator
Joined
Apr 11, 2008
Messages
3,421
Best answers
12
Likes
738
Location
Proland
#17
also your commits are related to some fixes/changes, mine are related to the first part of the downgrade
It doesn't matter what the commits are about, I was just illustrating how good commits look. I know you're just trying to learn here and it may not matter at all how you describe your commits.
But if you publish a link to your repository here and you hope to have other people look at it, use it or even contribute to that, you'd better create good commit messages. Some people may thank you for that. But if you make it really hard to find where you are doing what, then they will hate you.
 

StreamSide

Joseluis Gonzalez
Joined
Aug 31, 2007
Messages
3,082
Best answers
18
Likes
685
Location
Arica - Chile
#18
It doesn't matter what the commits are about, I was just illustrating how good commits look. I know you're just trying to learn here and it may not matter at all how you describe your commits.
But if you publish a link to your repository here and you hope to have other people look at it, use it or even contribute to that, you'd better create good commit messages. Some people may thank you for that. But if you make it really hard to find where you are doing what, then they will hate you.
Actually I will try to fix those commits doing just one big commit related to the first part of the downgrade, thanks for your information <3
 
Top