Skip to content

Releases: FracturedCode/XpBeacons

7.5 Minor text change

10 Dec 19:53
4f06f29
Compare
Choose a tag to compare
  • The command category "general beacon settings" is now named "general_beacon_settings"

7.4 Carpet API migration

10 Aug 04:33
606962f
Compare
Choose a tag to compare
  • update the extension to use the new api and translations system from carpet

7.3 1.20 update

05 Aug 21:12
eaa65ec
Compare
Choose a tag to compare
  • Compatible with 1.20.x and 1.19.x

7.2 1.19 update

08 Jul 20:06
cb6b1a8
Compare
Choose a tag to compare
  • Version bump for 1.19

7.1 Strength Parsing and 1.18.2

08 Mar 10:38
0b1e303
Compare
Choose a tag to compare

Thanks to @aria1th for the bug report and PR #13

  • Fix a parsing error for modified defaults in regards to the strength effect
  • 1.18.2 update

7.0 Completion and Uncapped Pyramid Level

06 Aug 09:29
57cc653
Compare
Choose a tag to compare

Changelog

  • Uncap the pyramid levels with beacon_max_pyramid_level
  • Configurable beacon_tick_rate
  • Change beacon radius settings to beacon_reach_multiplier
  • Add beacon_duration_multiplier
  • README changes
  • Backend carpet rule changes
  • Create a maven repository for artifacts

See the maven for all the artifacts.

6.0 Beacon Radius and New Xp Drain Rate Metric

28 Jul 02:07
b780582
Compare
Choose a tag to compare

Changelog

  • Beacon "radius", or rather half the side length that makes up the square of a beacon's useful area, is configurable per beacon level
  • Effect amplitude is now a minimum of 1, but will still be treated as 0 when applicable for xp drain. This way xp doesn't drain when your xp is low, but you still get a baseline effect.
  • xp drain rate is no longer an arbitrary multiplier. xp drain rate is measured in xp points removed per amplitude level
  • update README so there's no more HTML formatting issues from curseforge

v5.0 Xp Drain

23 Jul 01:00
Compare
Choose a tag to compare

I'm looking for feedback on this one. For example, what do you think about xp drain? Are the default values too aggressive? Did you just end up turning it off or turning it down?

Changelog

  • Add boolean rule <effect>_xp_drain which can toggle xp drain when near a beacon of the specified effect.
  • Add double rule <effect>_xp_drain_rate which can change the rate at which xp is consumed by the expression xp points drained per beacon tick = xp level * <effect>_xp_drain_rate
  • Fix broken carpet setDefault which would silently fail.

v4.1 Bug fix amplitude ceiling has validation

22 Jul 21:29
1cb735a
Compare
Choose a tag to compare

Changelog

  • All amplitude ceilings are now constrained by [0, 255], as this is what the game allows.

v4.0 Amplitude Ceiling and Effect Toggles

22 Jul 10:01
e3f9479
Compare
Choose a tag to compare

4.0 Changelog

  • Official server support
  • Per effect toggle
  • Per effect xp ceiling instead of blanket xp ceiling
  • Move from a "multiplier" system to a "max amplitude" system. This should be easier to understand. Now the effect amplitude is directly related to your xp from 0 to <effect>_amplitude_ceiling.
  • Backend, the settings class was reworked the best I could to fit within the confines of carpet commands
  • Move from MIT license to LGPLv3.0