[DiscordArchive] if it ignores movement data but it still works then that means its not needed no ?
[DiscordArchive] if it ignores movement data but it still works then that means its not needed no ?
Original source
if it ignores movement data but it still works then that means its not needed no ?
rektbyfaith
04-10-2024, 02:33 PM #1Archived author: Rymercyble • Posted: 2024-04-10T14:33:08.096000+00:00
Original source
if it ignores movement data but it still works then that means its not needed no ?
Original source
Well, the current implementation is indeed mostly useless.
rektbyfaith
04-10-2024, 02:33 PM #2Archived author: Natrist • Posted: 2024-04-10T14:33:59.420000+00:00
Original source
Well, the current implementation is indeed mostly useless.
Original source
I’m not sure how Blizzard would handle that kind of situation but I believe they disconnect you whenever something fishy is going on because it’s pretty much the best way to deal with the issue. It stops the cheater from further tampering in the moment and from a programming standpoint it’s also the easiest way to deal with it, so it’s a win-win.
rektbyfaith
04-10-2024, 02:35 PM #3Archived author: Natrist • Posted: 2024-04-10T14:35:33.378000+00:00
Original source
I’m not sure how Blizzard would handle that kind of situation but I believe they disconnect you whenever something fishy is going on because it’s pretty much the best way to deal with the issue. It stops the cheater from further tampering in the moment and from a programming standpoint it’s also the easiest way to deal with it, so it’s a win-win.
Original source
Additionally, I would log the number of disconnects and take action on the account when you reach a set threshold like say 3-5 disconnects.
rektbyfaith
04-10-2024, 02:37 PM #4Archived author: Natrist • Posted: 2024-04-10T14:37:37.497000+00:00
Original source
Additionally, I would log the number of disconnects and take action on the account when you reach a set threshold like say 3-5 disconnects.
Original source
Ban first for 3 hours, then 6, 12, 24, 48, 72, etc.
rektbyfaith
04-10-2024, 02:38 PM #5Archived author: Natrist • Posted: 2024-04-10T14:38:04.514000+00:00
Original source
Ban first for 3 hours, then 6, 12, 24, 48, 72, etc.
Original source
Something like what Blizzard had in place.
rektbyfaith
04-10-2024, 02:38 PM #6Archived author: Natrist • Posted: 2024-04-10T14:38:18.221000+00:00
Original source
Something like what Blizzard had in place.
Original source
That can all be automated and then Game Masters can decide to lock up the account permanently if need be.
rektbyfaith
04-10-2024, 02:38 PM #7Archived author: Natrist • Posted: 2024-04-10T14:38:50.838000+00:00
Original source
That can all be automated and then Game Masters can decide to lock up the account permanently if need be.
Original source
Can we setup GitHub CI checks to be „rerun“able?
In GitHub desktop there’s a button to re run checks, but until now it never wanted to do anything on my side
rektbyfaith
04-10-2024, 03:36 PM #8Archived author: sudlud • Posted: 2024-04-10T15:36:59.412000+00:00
Original source
Can we setup GitHub CI checks to be „rerun“able?
In GitHub desktop there’s a button to re run checks, but until now it never wanted to do anything on my side
Original source
It's a one line edit to the workflows
rektbyfaith
04-10-2024, 03:43 PM #9Archived author: Foe • Posted: 2024-04-10T15:43:14.862000+00:00
Original source
It's a one line edit to the workflows
Original source
we have the option to rerun them, not sure what you mean exactly
rektbyfaith
04-10-2024, 05:12 PM #10Archived author: Nyeriah • Posted: 2024-04-10T17:12:41.780000+00:00
Original source
we have the option to rerun them, not sure what you mean exactly
1 Guest(s)
1 Guest(s)