Implement VL scaling for Simulation#90
Open
GigaZelensky wants to merge 36 commits intoAxionize:lightningfrom
Open
Implement VL scaling for Simulation#90GigaZelensky wants to merge 36 commits intoAxionize:lightningfrom
GigaZelensky wants to merge 36 commits intoAxionize:lightningfrom
Conversation
- Add basic runtime reloading support. - Will only actually reload if current database is different/has different setting than the one requested in config. - Added [log] statements matching [alert] statements
…ierce) - Reduce unnecessary reach vectors used for calculations in versions
Notes: - Mark actions builds automatically as alpha on Modrinth - Shorten Fabric version string to be same as Bukkit on Modrinth
- Update gradle buildscript to not include branch-name if branch is called "lightning"
- Update GitHub Actions to automatically include changelog and to rename the jar LightningGrim-${platform}-${version}.jar
- Mark Paintings as entities that cannot be hit to prevent EntityPierce (formally HitboxEntity) falses.
- 2.2x reduction in queued task overhead
- reduction in size of queued single block changes
- up to 8x reduction in size of queued multi block changes
- fixed blocks disappearing in B73 caused by incorrect shifting in new block udpate handler
* "Wall Hit" -> "WallHit"
* "Entity Pierce" -> "EntityPierce"
* Fix modeling experience orb as unhittable entity
* Fix sending hitbox with /grim hitboxdebug in the hitboxdebug handler
* Update upstream to 35811fe
- Add basic runtime reloading support. - Will only actually reload if current database is different/has different setting than the one requested in config. - Added [log] statements matching [alert] statements
…ierce) - Reduce unnecessary reach vectors used for calculations in versions
Notes: - Mark actions builds automatically as alpha on Modrinth - Shorten Fabric version string to be same as Bukkit on Modrinth
- Update gradle buildscript to not include branch-name if branch is called "lightning"
- Update GitHub Actions to automatically include changelog and to rename the jar LightningGrim-${platform}-${version}.jar
- Mark Paintings as entities that cannot be hit to prevent EntityPierce (formally HitboxEntity) falses.
- 2.2x reduction in queued task overhead
- reduction in size of queued single block changes
- up to 8x reduction in size of queued multi block changes
- fixed blocks disappearing in B73 caused by incorrect shifting in new block udpate handler
* "Wall Hit" -> "WallHit"
* "Entity Pierce" -> "EntityPierce"
* Fix modeling experience orb as unhittable entity
* Fix sending hitbox with /grim hitboxdebug in the hitboxdebug handler
* Update upstream to 35811fe
This reverts commit 4d6c9c6.
…s-for-config-options Codex/add translated comments for config options
Author
So I added a millisecond delay option which was requested by a user (heckergato), the objective is to have a smoother command execution when multiple VLs are fired at once due to VL scaling. I also added an option which I will explain here:TL;DR: The punishment system tracks how many times a command is executed ( Example:
Why? Because the Grim thinks, “Ah, I already ran this command once for VL 20, no need to do it again.” Even though the VL dropped and came back up, which should be treated as a new violation threshold being reached. Why This Sucks:
What Should Happen:
This is exactly what I have also implemented as a config option. |
Axionize
force-pushed
the
lightning
branch
2 times, most recently
from
2582e6c to
4ff4a27
Compare
Axionize
force-pushed
the
lightning
branch
5 times, most recently
from
0763048 to
326e200
Compare
Axionize
force-pushed
the
lightning
branch
2 times, most recently
from
037abab to
71d93c9
Compare
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
2 participants
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.
(Title)
Makes it so you can set grim to add more levels for simulation per violation depending on the offset in the prediction/actual comparison.
Fixes the punishment decay issue that was present in WHY-HAVE-YOU-SUMMONED-ME's PR (GrimAnticheat#1961).
Nothing else is changed.
Also includes translations for the configs which I think are pretty solid but anyone can feel free to change them later.
(I just PR'd to upstream Grim but this makes it easier for you to merge since it already has everything lightning has)