Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help Me: Wave Wallet claim time #301

Open
nileshpk opened this issue Jan 18, 2025 · 3 comments
Open

Help Me: Wave Wallet claim time #301

nileshpk opened this issue Jan 18, 2025 · 3 comments

Comments

@nileshpk
Copy link

Introduction:
Hi Sir, is wave wallet consider time for next claim. As I upgraded it to 24 hours but after successful claim it does not wait for 24 hours. and it automatically intiate reclaim in every one or two hours. due to this no session left for new game. I have set max concurrent claims 4.

Image

Which self-help guides have you tried to follow? (required):
Please list the guides or resources you've consulted so far.

Describe Your Issue (required):
Please provide a clear and concise description of the help you need.

Have you checked the FAQ (required):
Before submitting, please confirm that you've reviewed the FAQ linked above.

Steps Taken So Far (optional):
Describe what you have tried so far to resolve your issue.

Additional Information:
Include any other information that might help us assist you, such as screenshots, logs, or system details.

@thebrumby
Copy link
Owner

Hi nileshpk,

As I upgraded it to 24 hours but after a successful claim, it does not wait for 24 hours and automatically initiates reclaim every one or two hours.

The wave script should wait for the exact duration specified by the game before initiating another claim. If it doesn't, this might be due to a script crash or restart, which could bypass the intended timer. It’s worth double-checking the script's error handling and logging to ensure the timer resets correctly after each successful claim.

Due to this, no session is left for a new game. I have set the max concurrent claims to 4.

Does your server have sufficient RAM and CPU resources to handle 4 concurrent sessions? As a general guideline, you’d need at least 6 GB of RAM and a 4-core processor for smooth operation at this level. If the screenshot you shared was taken within a Docker container, ensure there are enough resources allocated to all containers on the host system. Insufficient resources could cause instability or unintended behavior.

@thebrumby
Copy link
Owner

If you type:

pm2 list

You should be able to see how many times the script is restarting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
@thebrumby @nileshpk and others