[ImgBot] Optimize images

[imgbot[bot]]

Beep boop. Your images are optimized!

Your image file size has been reduced by 20% 🎉

Details

File	Before	After	Percent reduction
/src/main/resources/assets/skytils/toasts/keys/blood.png	6.15kb	2.46kb	60.02%
/src/main/resources/assets/skytils/crystalhollowsmap.png	193.74kb	79.41kb	59.01%
/src/main/resources/assets/skytils/textures/dungeons/m7/dragon_flame.png	13.57kb	6.07kb	55.24%
/src/main/resources/assets/skytils/textures/dungeons/m7/dragon_soul.png	13.27kb	6.05kb	54.44%
/src/main/resources/assets/skytils/textures/dungeons/m7/dragon_apex.png	13.11kb	6.01kb	54.14%
/src/main/resources/assets/skytils/textures/dungeons/m7/dragon_ice.png	13.05kb	6.05kb	53.65%
/src/main/resources/assets/skytils/textures/dungeons/m7/dragon_power.png	12.73kb	6.05kb	52.46%
/src/main/resources/assets/skytils/toasts/combo/luck.png	2.41kb	1.44kb	40.00%
/src/main/resources/assets/skytils/toasts/keys/wither.png	6.11kb	3.70kb	39.49%
/src/main/resources/assets/skytils/toasts/combo/coin.png	2.15kb	1.40kb	35.04%
/src/main/resources/assets/skytils/abdpfp.gif	299.09kb	197.15kb	34.08%
/src/main/resources/assets/skytils/toasts/combo/combat.png	0.69kb	0.52kb	24.65%
/src/main/resources/assets/skytils/toasts/blessings/time.png	11.55kb	10.55kb	8.62%
/src/main/resources/assets/skytils/toasts/blessings/stone.png	13.42kb	12.37kb	7.79%
/src/main/resources/assets/skytils/toasts/blessings/wisdom.png	11.70kb	10.83kb	7.45%
/src/main/resources/assets/skytils/toasts/blessings/power.png	11.58kb	10.74kb	7.26%
/src/main/resources/assets/skytils/toasts/blessings/life.png	12.93kb	12.14kb	6.10%
/src/main/resources/assets/skytils/gui/rarity2.png	5.41kb	5.19kb	3.97%
/src/main/resources/assets/skytils/toasts/revive.png	33.62kb	32.31kb	3.89%
/src/main/resources/assets/skytils/icons/SUMMONING_EYE.png	4.98kb	4.85kb	2.59%
/src/main/resources/assets/skytils/jamcat.gif	359.04kb	354.70kb	1.21%
/src/main/resources/assets/skytils/azoopet.gif	28.87kb	28.57kb	1.02%
/src/main/resources/assets/skytils/sychicpet.gif	109.75kb	108.72kb	0.94%
/src/main/resources/assets/skytils/partysychic.gif	104.39kb	103.71kb	0.64%
/src/main/resources/assets/skytils/christmassychicpet.gif	104.26kb	103.63kb	0.60%
/src/main/resources/assets/skytils/icons/dolphin.png	2.13kb	2.12kb	0.32%
Total :	1,389.68kb	1,116.77kb	19.64%

---

📝 docs | :octocat: repo | 🙋🏾 issues | 🏪 marketplace

~Imgbot - Part of Optimole family

[pull-request-quantifier-deprecated[bot]]

This PR has 0 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : No Changes
Size       : +0 -0
Percentile : 0%

Total files changed: 0

Change summary by file extension:

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

[pull-request-quantifier-deprecated[bot]]

This PR has 5259 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Large
Size       : +4394 -865
Percentile : 100%

Total files changed: 64

Change summary by file extension:
.yml : +19 -22
.gitignore : +0 -89
.kts : +0 -212
.properties : +0 -22
.java : +884 -432
.kt : +3491 -0
.json : +0 -88

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.