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

Storm collision error #2832

Closed
PolSpock opened this issue Jan 30, 2019 · 3 comments
Closed

Storm collision error #2832

PolSpock opened this issue Jan 30, 2019 · 3 comments

Comments

@PolSpock
Copy link

Description of the bug

When meteor storm are enabled and when a meteor hit the ground, a game error is printed to the console for each meteor collision.

How to make the bug happen

With no addon & workshop addon :
Enable the meteor storm, wait for the meteor to fall the ground.

By my investigation, when meteor touch a solid thing, PhysicsCollide() of meteor ent is called. So self:Destruct() is called. And when serv hit the 'self:Remove()' line, the error appear.

Lua errors

meteor[320]: Changing collision rules within a callback is likely to cause crashes!

Why the developer of DarkRP is responsible for this issue

The meteor system is developed by DarkRP developers 😃

Regards,

@Bo98
Copy link
Contributor

Bo98 commented Jan 30, 2019

Nice spot.

I can't believe there's still not a proper API for this (Facepunch/garrysmod-requests#894) so a hack using timers may be the only way to avoid this.

@TomDotBat
Copy link

Lmao people actually use the built in meteor storm?

@FPtje
Copy link
Owner

FPtje commented Jan 31, 2019

I can imagine the ones who do are among the best ones

@FPtje FPtje closed this as completed in b3fadd0 Feb 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants