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

feat: more robust zone handling #1524

Merged
merged 2 commits into from
Aug 29, 2023
Merged

feat: more robust zone handling #1524

merged 2 commits into from
Aug 29, 2023

Conversation

luan
Copy link
Contributor

@luan luan commented Aug 28, 2023

This adds a lot of safety to how we handle Zones. Making it so dealing with the contents of a zone is never going to respond with creatures that have already been deleted.

This also migrated the bosslever.lua to use zones, and deprectes the Spectators library. Zones are a more flexible way to achieve the same thing, and more. This should also fix a potential crazy with the removal of players from a bosslever room since that was previously done with an unsafe call to addEvent.

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 6 Code Smells

0.0% 0.0% Coverage
5.3% 5.3% Duplication

@luan luan merged commit c8dd05b into opentibiabr:main Aug 29, 2023
JasterDesu pushed a commit to JasterDesu/canary that referenced this pull request Sep 16, 2023
This adds a lot of safety to how we handle Zones. Making it so dealing
with the contents of a zone is never going to respond with creatures
that have already been deleted.

This also migrated the `bosslever.lua` to use zones, and deprectes the
Spectators library. Zones are a more flexible way to achieve the same
thing, and more. This should also fix a potential crazy with the removal
of players from a bosslever room since that was previously done with an
unsafe call to `addEvent`.
@luan luan deleted the luan/boss-zones branch September 27, 2023 17:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants