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

Release 1.15 #365

Merged
merged 52 commits into from
Jan 20, 2024
Merged

Release 1.15 #365

merged 52 commits into from
Jan 20, 2024

Conversation

tastybento
Copy link
Member

No description provided.

tastybento and others added 30 commits October 22, 2023 03:44
tastybento and others added 22 commits November 10, 2023 08:26
 - Everytime new phase was set, plugin sent the first block of the phase 2 times.
 - CustomBlocks in fixedBlocks were causing issues where it was pushing the CustomBlock multiple times into queue.
 - Phase config was not refreshed when doing /isa reload. I tested it and I do not see any issues.

Refactors:
 - Variable naming refactors, because having name `obPhase` for `phase` instance + name `phase` for the `ConfigurationSection` was not really understandable (I changed it to `phaseConfig`)

Added features:
 - New `CustomBlock` for mobs in format:
 ```
 - type: mob
   mob: ZOMBIE
   underlying-block: GRASS_BLOCK
 ```
 It will spawn a mob on top of underlying block. I know that mob spawns are not exactly counted as "destroyed block", but in this case it is needed. It would not make sense setting it in fixedBlocks if not.
 - New `Requirement - cooldown` (seconds) that blocks new phase until time elapses.
Bug fixes & CustomBlock type for mob spawning
* Fixed:
 - `Requirement - cooldown` was not working properly

Refactors:
 - Minor refactors to `BlockListener.process` method for better readability

* Clarified that requirement value is in seconds

* - Moved `setNewPhase` back to `CheckPhase` class
 - Fixed tests
 - Refactored test run args as they were weirdly formatted

* Removed unused imports

---------

Co-authored-by: tastybento <[email protected]>
The only time this might be null is after loading from the database, and
is rare.
Put {} around the e.setCancelled(true) to make it clear that only this
statement is to be run.
* Translate uk.yml via GitLocalize

* Translate uk.yml via GitLocalize

* Translate uk.yml via GitLocalize

---------

Co-authored-by: GIGABAIT <[email protected]>
Co-authored-by: mt-gitlocalize <[email protected]>
Co-authored-by: BONNe <[email protected]>
* Let ItemsAdder be a new OneBlockCustomBlock

* fix conflict
* - Fixed `goToBlock` that was not working correctly after introducing `cooldown` requirement.

* Removed debug print. Opsie..
Copy link

@tastybento tastybento merged commit 27a9bcb into master Jan 20, 2024
3 checks passed
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

Successfully merging this pull request may close these issues.

7 participants