-
-
Notifications
You must be signed in to change notification settings - Fork 13
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Ceilings and Broadcast Precision (#168)
Squashed with the following changes: * Update Actions Toolchain, Add JDK 19 * Rework height-checks against flag base. * Add option to use precise location of a flag in broadcasts. * Update CHANGELOG.md Issues to be ironed out as they become apparent.
- Loading branch information
1 parent
5cdbad8
commit ef578a6
Showing
12 changed files
with
160 additions
and
39 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
# Working Doc: Issue 84 | ||
|
||
<!-- TODO: Delete this file before merge --> | ||
## Impossible to attack a plot that has blocks placed at world build-height limit. | ||
|
||
- [GitHub](https://github.com/TownyAdvanced/FlagWar/issues/84) | ||
|
||
### Summary | ||
|
||
If an attacking player is attempting to flag a plot, and a ceiling exists | ||
above the flag location, the flag will not be placeable. Some defending | ||
players will take advantage of this fact by placing a plot-wide ceiling | ||
at a world's maximum build height. | ||
|
||
This issue also extends to worlds with natural ceilings such as worlds | ||
using the default Nether generator settings. | ||
|
||
This issue stems from design decisions as old as the general-audience | ||
release of the game. As such, this issue is a natural bug. It is also | ||
classified as a blocker for future official FlagWar releases due to its | ||
exploit-ability. | ||
|
||
### Proposed Solution | ||
|
||
This issue should be easily addressed by applying a few hard-coded rules | ||
to when and where a war-flag may be placed. | ||
|
||
- [x] Allow placing flags under ceilings. (Required) | ||
- [x] Traditional check: In a world without a natural ceiling, and the highest block is within 5 meters of max height. | ||
- [x] Add a basic height check: | ||
- [x] (submersion) checks for if a flag base has a liquid up to 4 meters above it | ||
- [x] (general space) check same vertical space for any non-empty, non-liquid blocks | ||
- [x] Add sea-level (minus depth) check | ||
- Flag base must be at or above a world's sea-level, minus modifier. | ||
- Default modifier: 12 meters | ||
|
||
- [x] Rework Coordinate Broadcasting | ||
|
||
- [ ] ~~Specific Audience Options (_Config_)~~ | ||
- This specific plan was scrapped. | ||
- [x] Location Accuracy (_Config_) | ||
- towny (_Towny Coord, default_) | ||
- precise (_Minecraft's X,Y,Z_) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters