-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing a few attributes in item description code #4670
Comments
Can you elaborate this more, I don't want to be rude but your text is heavily confusing, provide also some sample code |
E.g. there is:
but at the same time a code that was omitted:
etc. Then it would be good to remove those if's and put them into separate method:
I think that some of abilities.stats and abilities.statsPercent are missing. Maybe some others too. |
Yea I agree the monstrosity of that should have been re worked already. |
I guess I was sent slightly older src, as currently tfs has moved that into lua. So it doesn't really matter anymore. It's still 600+ lines method there, so it still could be broken into smaller segments (https://github.com/otland/forgottenserver/blob/master/data/lib/core/item.lua#L151), but atleast there are comments included. |
Before creating an issue, please ensure:
support matter (use https://otland.net/forums/support.16/ for support)
Steps to reproduce (include any configuration/script required to reproduce)
Its not technically a bug, but TFS's forgotten&unfinished feature
Expected behaviour
Whole Item::getDescription from item.cpp, should be reworked.
By that I mean divided into methods like,
The idea of maxhealthpoints and other stats like +X% of magic damage is TFS's custom thing. Tibia doesnt have it.
But it is there (been for decades), so it should be fully finished, not only partly.
Also, if this comes through, the "protection" wording should also change.
Tibia's style is listing protections in a way:
protection earth +5%, holy +5%, earth -3%
/\ all those are protections listed.
But the +5% earth <- damage for example could be confusing in that case, so maybe each protection should be preceded by either "prot" or "protection" word.
Feel welcome to discuss. It's easy to finish and PR this, but Imo first it should be known what direction should this code go in.
The text was updated successfully, but these errors were encountered: