Core Progressionsource backed10 minute read

Stamina System

The 42-hour stamina clock, premium bonus band, ordinary and reduced experience bands, offline regeneration, loot implications, and server-specific audit checklist.

Reference profileOfficial rules and TFS 1.6 reference scripts
Reviewed
Evidence5 primary references

At a glance

Quick facts

Maximum
42 hours / 2,520 minutes
Bonus band
Above 39 hours, premium characters receive 150% monster experience in the reference profile
Low band
At or below 14 hours, monster experience is reduced to 50%
Regeneration delay
Begins after 10 minutes offline in the reference script

Stamina bands

Reference stamina bands
Stamina remainingMonster experienceAdditional behavior
39:00 to 42:00150% for premium characters; otherwise ordinary rateOften called bonus or happy hours
14:01 to 39:00100%Ordinary stamina band
00:01 to 14:0050%Official rules also restrict monster loot when the top-damage character is in this band
00:00No monster experience in the TFS reference pathServer scripts may add further restrictions

The stock TFS gain-experience event reads stamina after consumption for the current gain and applies the multiplier. Exact boundary behavior should be tested on the deployed fork, particularly at 39:00 and 14:00, because scripts can consume and evaluate in a different order.

Consumption follows rewarded monster activity

In the reference event, stamina is consumed when experience is gained from a non-player source. The script tracks time between eligible gains and subtracts one or two minutes depending on elapsed time, preventing every individual monster from consuming a full minute. Player-sourced experience does not enter this event branch.

Offline regeneration

The TFS 1.6 login script subtracts a 10-minute waiting period from offline time. After that delay, ordinary stamina up to 39 hours regenerates at one stamina minute per three offline minutes. The final three bonus hours regenerate at one stamina minute per six offline minutes. The script caps stamina at 42 hours and caps a single offline interval considered for recovery at 21 days.

Ordinary-band recovery after the delay
Recovered ordinary minutes = floor(max(0, OfflineSeconds - 600) / 180)
  • Recovery stops at 2,340 stamina minutes before the bonus-band rule applies.
  • Configured timeToRegenMinuteStamina can replace 180 seconds.
Bonus-band recovery after ordinary stamina is full
Recovered bonus minutes = floor(RemainingEligibleOfflineSeconds / 360)
  • The final cap is 2,520 stamina minutes.
  • Configured timeToRegenMinutePremiumStamina can replace 360 seconds.
Recovery examples after the 10-minute delay
Starting staminaOffline durationReference recovery
20:0070 minutes20 ordinary minutes, reaching 20:20
38:5070 minutes10 ordinary minutes to 39:00, then about 5 bonus minutes
41:5070 minutes10 bonus minutes, reaching the 42:00 cap

Plan sessions around goals, not only bonus hours

  • Use bonus stamina on the highest-value experience session if level progression is the goal.
  • Ordinary stamina can be better for access quests, bestiary completion, gathering, trading, or low-risk exploration.
  • Avoid entering the low band before a loot-dependent hunt unless the server explicitly overrides the official loot restriction.
  • Account for the slower six-to-one recovery of the final three hours when planning daily sessions.
  • On seasonal servers, compare stamina policy with paid boosts and multi-character play because those systems change competitive pressure.

Server stamina disclosure checklist

  • Is the stamina system enabled?
  • What are the maximum, bonus threshold, low threshold, and exact multipliers?
  • Does low stamina remove loot, experience, both, or neither?
  • Which experience sources consume stamina and which receive the multiplier?
  • What offline delay and recovery ratios apply?
  • Can resting zones, beds, daily rewards, store items, or premium status regenerate stamina online?

Apply the guide

Find servers using this profile

Server names, protocol labels, and map labels do not guarantee matching mechanics. Use these filters to find candidates, then verify the listing, owner documentation, and deployed ruleset.

long termlow ratepremium staminaseasonal1x