Skip to content

Releases: eggohito/origins-limiter

v3.1.0

03 Apr 02:05
9a7a85c
Compare
Choose a tag to compare

Changelog

  • Renamed origins-limiter:uninstall to origins-limiter:clean_up
  • Renamed origins-limiter:private/update_interval/sync function to origins-limiter:private/sync/update_interval
  • Changed how config stuff are handled
  • Added replace boolean fields to origin layers
  • Added a 3-tick delay before giving the Orb of Origin back

Notes

Releases marked with 'API' is only meant for users that wish to integrate the datapack library into their own datapack.

v3.0.0

07 Mar 00:13
d27254f
Compare
Choose a tag to compare

Changelog:

  • Refactored confirmation implementation (again and again)
  • Fixed an issue where the limiter system prevents you from choosing an origin that isn't registered in the limiter system

v2.3.1

04 Feb 14:41
bdd2214
Compare
Choose a tag to compare

Changelog:

  • Fixed a bug where you can obtain multiple Orbs by selecting origins that have reached their max count in multiple origin layers

v2.3.0

03 Feb 02:49
879fe8f
Compare
Choose a tag to compare

Changelog:

  • Changed the file structure of the pack
    • The structure and name of the folders and functions should be pretty consistent now
  • Re-did the implementation for the override and cancel features
    • You can now choose an origin in a different layer if that layer is not registered in the datapack library. Previously, it would just fully prevent you from having an origin from all layers

v2.2.0

12 Jan 08:19
Compare
Choose a tag to compare

Changelog:

  • Refactored the confirmation and status origin layers to follow a new format:
    • origins-limiter:confirm/<namespace>/<layer_id>.json
    • origins-limiter:status/<namespace>/<layer_id>.json
  • Refactored the override feature
  • Generalized the cancel message

v2.1.0

13 Dec 12:58
Compare
Choose a tag to compare

Changelog:

  • Added an override feature that lets you pick the origin that you chose without being restricted.
    • To apply the override, you can add the origins-limiter.override tag to the player
  • Changed the way how the confirmation system works

v2.0.0

12 Dec 08:11
Compare
Choose a tag to compare

Changelog:

  • Moved the advancements to origins
    • Since the base origins are added by the origins namespace
  • Refactored can_pick functions
    • Moved the function files to the origins sub-folder
    • Renamed the score holders to have the origins namespace prepended to it
  • Refactored the cancel origin and power files
    • To follow the new format: <namespace>/<layer_name>/cancel.json
  • Refactored confirm origin layer
    • To follow the new format: <namespace>/<layer_name>.json
  • Refactored the cancel JSON text component
  • Change the order of the confirm origin layer

v1.4.0

07 Dec 10:36
Compare
Choose a tag to compare

Changelog:

Nothing much has changed this time, just little tweaks here and there.

  • Added root.msg.cancel JSON text component in the origins-limiter:main storage. Mainly used for displaying a message to a player when cancelling the origin picking process.
  • Slightly changed semver implementation. It's slightly better than the previous implementation
  • Changed names and descriptions of the used origin layers, origins, etc.
  • Make the confirm/origin origin layer automatically choose an origin, and make it hidden (for 1.17+ only)

Note

origins-limiter_* should be compatible with 1.17.x and above. If you're still using 1.16.x, please use origins-limiter_1.16_*!

v1.3.0

22 Sep 09:42
Compare
Choose a tag to compare

Changelog:

  • Renamed .cfg to config
    • For consistency with my other packs
  • Added pre and post cancel function tags
    • For running functions before, or after cancelling the origin. Gives the user a bit more control on events they wish to run upon cancelling the origin picking process

v1.2.0

28 Aug 13:22
Compare
Choose a tag to compare

Changelog:

  • Added 'cancel' function tag, used for running functions that can remedy edge-case issues when cancelling origins
  • Tweaked semver implementation because the old one is bonkers