More of a concern than an issue

[Kaizuk-O]

Recently the server has switched to Togglesnipe 2 with 1.5 second timer - the settings for the channel has been updated respectively as shown in the attached images.

However, after every roll it will show valueError and a bunch of other messages relating to get_snipe_time and snipe_delay and things like that as shown in the first image.

As of right now, no wishes have dropped, and it still claims kakera as it should.

Is there anything in those messages that should raise concern?

[Kaizuk-O]

Update: A wish of mine appeared and it was not able to claim or even attempted to claim

I wasn't there for this so I didn't see exactly what happened, but before the togglesnipe came into play this would've claimed no problem

[Kaizuk-O]

Update: the additional error type messages that show up after every roll seem to only coming up when I have claim - when I no longer have claim it shows someone else rolled in the channel as normal

The first few rolls at the start of the screenshot are when I don't have claim, the last one is after my claim time has reset.

When a wish shows up, the script isn't able to pick it up likely due to the message it shows when I do have claim.

Any advice?

[vivinano]

Basically the claim delay is getting to many variables and not getting proper settings let me test when I change mine to a value with a decimal it might be an easy fix we shall see another work around is to set ur 1.5 > 2 so that way it can still snipe

Sent from my iPhone

On Aug 17, 2021, at 11:04 AM, Kaizuk-O @.***> wrote:

 Update: the additional error type messages that show up after every roll seem to only coming up when I have claim - when I no longer have claim it shows someone else rolled in the channel as normal

The first few rolls at the start of the screenshot are when I don't have claim, the last one is after my claim time has reset.

When a wish shows up, the script isn't able to pick it up likely due to the message it shows when I do have claim.

Any advice?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[Kaizuk-O]

Yep, I just tested it in a server with 3 sec delay instead of a number with a decimal number and it seems to be fine.

For a server using 2 sec, 3sec, 4sec. etc. delay; what would you say is the best claim delay to use in the Settings_mudae.json file to ensure it still claims as instantly as it can?

[vivinano]

alright I've push code changes the new revision to support decimal numbers in $settings if found

2cff11b930cd742f9ca4b7a7e0e1bd3cd9a679db

with this change I will be closing this issue as since it should now finally support decimal numbers

also since i know this will probably be a follow up question based on many other "issues"

there is a small .5 delay added on all snipe times this is because interaction that are instant or Extremely fast will not be registered by mudae you can feel free to remove this extra added time but it might lower consistency