Post: #4

(01-28-2017 04:04 PM)Coruja Wrote:  this is considered an bugfix rather than an "new change", as already documented on changelog:

Code:

17-06-2015, Coruja
...
Fixed: Properties like STR/ModSTR/MaxHits/etc making the char have current status value > max allowed value when the status got lowered.

the correct UO behavior is never allow the current status value be higher than its maximum value. Previously sphere was allowing values higher than max value, but on 56c it got fixed and now if the max value get decreased, sphere will decrease the current value too to prevent "CurrentValue > MaxValue"

anyway, this fix can be easily changed manually on source, just take a look on CCharSkill.cpp, functions CChar::Stat_AddMod(), CChar::Stat_SetMod(), CChar::Stat_SetMax() and CChar::Stat_SetBase()

PS: just don't forget to change the build type from "Nightly/Release" to "Local" on the compiler, because nightly/release builds are reserved for official builds and should not be used on non-official builds with custom changes. Instead, "Local" builds must be used for this purpose to clearly display to players that the server is running using an local (custom) source code

I see, i would not be able to deduce from that line of the changelog that this bugfix meant that, talking in practical effects.

Thanks for your reply and enlightenment !! I Appreciate your time