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

[Bug|Crash]: Forbidden Strenght Orbs cause the Servers TPS to Tank to 0 #1826

Open
4 tasks done
Mikaaah opened this issue Sep 29, 2024 · 2 comments
Open
4 tasks done
Labels
planned We are aware of the issue and will fix in the future

Comments

@Mikaaah
Copy link

Mikaaah commented Sep 29, 2024

Please check if a similar issue has already been reported.

  • I checked this type of issue has never been reported.

Please check you're using proper versions.

  • I checked all of them in the right version.

Please check if this issue's from out of our area

  • I understood the problem.

The name of the mod

No response

After all of these, please check if you're just pressing the ok buttons to skip this process.

  • I read the checklist and I promise I'll provide all the information that is needed to fix the issue

Minecraft Version

1.20.1

The Issue

When a epicfight:forbidden_strength_orb spawns it instantly drops the servers tps to 0, this issue is consistent, and happens every time.

https://observable.tas.sh/p/I6Ha/aggregated
epicfight:forbidden_strength_orb x1 | 13363947 μs (99.2%)

Steps to Reproduce

When using the deathharvest skill, and getting the hit that spawns the orb, it instantly kills the servers tps.

@Yesssssman Yesssssman added the planned We are aware of the issue and will fix in the future label Oct 10, 2024
@Yesssssman
Copy link
Owner

I'm not sure of the reason but I optimized the ticking code of the entity. Could you test this on the next update?

@Yesssssman
Copy link
Owner

Hi, can you test if the same issue exists in 20.9.3?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
planned We are aware of the issue and will fix in the future
Projects
None yet
Development

No branches or pull requests

2 participants