Difference between revisions of "User talk:Smeister"

1,404 bytes added ,  19:15, 22 May 2006
no edit summary
imported>Halo112358
m
imported>JT
 
Line 25: Line 25:


(Constrast: the mod that I have "inherited," I guess, aims to make you regenerate slowly when you are weak and quickly when you are strong by using a formula like healthGivePeriod = 1 - curhp / maxhp. As I understand it, maxhp (not to be confused with base) cannot be found by any decent means?)
(Constrast: the mod that I have "inherited," I guess, aims to make you regenerate slowly when you are weak and quickly when you are strong by using a formula like healthGivePeriod = 1 - curhp / maxhp. As I understand it, maxhp (not to be confused with base) cannot be found by any decent means?)
----
I'd like to point out that artificial restrictions are probably one of the worst things out there.  You need to provide at least ''some'' programmatical way of changing the Magic, Game, and Script Modifiers, or else the variables are all but worthless.  Call me a curmudgeon if you'd like, but not having direct access to these modifiers causes mores problems than it fixes... I absolutely don't agree with the "that would definitely break the game in horrible ways" comment, because for that to be true it would have to be ''misused''.  If someone breaks the game, ''it's their own fault''.  The Construction Set isn't supported by Bethesda's Tech Support anyway, after all. =)
As for the problem Decoup had on [[Talk:ModActorValue]], I couldn't agree more.  A set of ModCurrentHealth/Fatigue/Magicka and SetCurrentHealth/Fatigue/Magicka functions would be extremely useful: functions which modify the ''current'' value, such that the value can restore itself over time.  I'm even tempted to say "necessary" as opposed to "useful"; we had access to these in Morrowind, so it's surprising they weren't implemented in Oblivion.  There are millions of situations where scripts could apply temporary losses to actors and where using a full-on [[Cast]] command would be inappropriate.
I may be biased because I ran into this problem in my latest plugin... --[[User:JT|JT]] 20:15, 22 May 2006 (EDT)
Anonymous user