-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Siege Improvements #30
Conversation
src/main/java/net/countercraft/movecraft/warfare/features/siege/SiegeLeaderListener.java
Outdated
Show resolved
Hide resolved
src/main/java/net/countercraft/movecraft/warfare/features/siege/SiegeLeaderListener.java
Outdated
Show resolved
Hide resolved
src/main/java/net/countercraft/movecraft/warfare/features/siege/SiegeLeaderListener.java
Outdated
Show resolved
Hide resolved
Bukkit.getServer().broadcastMessage(String.format(I18nSupport.getInternationalisedString("Siege - Sudden Death"), | ||
siege.getName(), (timeLeft+2)/60)); | ||
if (!siege.leaderIsInControl()) { | ||
endSiege(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Won't this cause the siege to end twice since it's also ended in SiegeLeaderListener
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, because the SiegeLeaderListener one specifically fires when a craft is sunk or released, whereas the SiegeProgressTask one fires when sudden death begins and there is no flagship detected.
We also need to resolve the merge conflicts |
whoops
added priorities to all events, set them to ignore cancelled
This PR makes a few changes to the siege system to help automatically enforce certain rules, such as siege leaders not being allowed to leave the box and siege sudden death.
It also makes some minor changes to the siege announcements to provide players with more information and fixes some grammatical errors that were really bugging me.
This will close #24