Conversation
This updates the player login script to initialize stamina, XP stamina, and concoction cooldown timers using the current Unix time instead of a hardcoded 1. This ensures cooldown tracking starts from the actual login moment and prevents immediate reuse or incorrect timing behavior.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The problem:
Hardcoded 1 means "epoch time" (1970). If cooldown checks compare os.time() >= NextUseStaminaTime[playerId], the value 1 is always less than current time (~1.7 billion), so the cooldown is always expired — players can immediately reuse stamina/XP/concoction after login, bypassing intended cooldowns.
The fix:
Setting to os.time() starts the cooldown from the actual login moment. If the code later adds cooldown duration (e.g., NextUseStaminaTime[id] = os.time() + cooldownSeconds), it works correctly.