Lua Stamina PROBLEM,IT DONT UP!REP+

[chele242]

Hello ppl.

I got problem, players say me stamina doesnt up, it down, but no up.

-- Stamina
	rateStaminaLoss = 1
	rateStaminaGain = 1000 / 3
	rateStaminaThresholdGain = 4
	staminaRatingLimitTop = 41 * 60
	staminaRatingLimitBottom = 14 * 60
	rateStaminaAboveNormal = 1.5
	rateStaminaUnderNormal = 0.5
	staminaThresholdOnlyPremium = "yes"

There is mine stamina rate, Anyone know how fix it good? I give rep+ and Thanks

 

[exique]

They need to be offline...

 

[chele242]

OFC i know that.. But it not up..

 

[Rexxar]

Try changing

rateStaminaGain = 1000 / 3

to

rateStaminaGain = 300

Because 1000 divided by 3 equals to something like:

333.3333333333333333333333333333333333333333333333

Into all infinity.
This might confuse the server when it tries to calculate how fast the player shall gain stamina, and thus they end up regenerating no stamina at all.

Of course this is just a guess.

 

[frankfarmer]

	-- Stamina
	rateStaminaLoss = 1
	rateStaminaGain = 1000 / 4
	rateStaminaThresholdGain = 4
	staminaRatingLimitTop = 41 * 60
	staminaRatingLimitBottom = 14 * 60
	rateStaminaAboveNormal = 1.0
	rateStaminaUnderNormal = 1.0
	staminaThresholdOnlyPremium = "yes"

You can also remove stamina from your OT, because it sucks

	[COLOR="Red"]rateStaminaLoss = 1[/COLOR]

to

	[COLOR="Red"]rateStaminaLoss = 0[/COLOR]

 

[exique]

Try changing

Lua Code:

rateStaminaGain = 1000 / 3​

to

Lua Code:

rateStaminaGain = 300​

Because 1000 divided by 3 equals to something like:

333.3333333333333333333333333333333333333333333333

Into all infinity.
This might confuse the server when it tries to calculate how fast the player shall gain stamina, and thus they end up regenerating no stamina at all.

Of course this is just a guess.

Might work. But all the 'pro' calculators irl says that 10 / 3 = 3

 

[AchTung]

Lol Stamina ain't sucky lol since it prevent mass botters.

 

[Rexxar]

Might work. But all the 'pro' calculators irl says that 10 / 3 = 3

Well, at least all calculators and programs I've worked with, has always truncated the number down to the max number of digits the variable/screen can handle.

I just figured that using a possible floating point number as value for rates-calculations, could cause unexpected issues.