VaultAdditions v1.4.0

VaultAdditions v1.4.0

oh god this is gonna be a big one huh?

• Completly overhauled the Event system

• Events are no longer hardcoded alongside their modifiers

• Added Event IDs:

  • vaultadditions:event_re_enable_border_expansion
    • This event re-enables the Border Expansion event for the given Event Duration, as it did in the previous version
  • vaultadditions:event_add_portal_modifiers
    • This event applies the configured modifiers in the new config file to portals entered in the events timespan
    • Previously, these were hardcoded for 5 total events with each corresponding modifier, this is no longer the case, and the modifiers can be configured to any modifier desired

• Event entries are no longer added via command

• Event entries are now based inside a new Config inside the config/the_vault/vaultadditions_events.json file

• This config allows for the following for each entry:

  • Specification of the eventId between the aforementioned EventIDs
  • the eventStartMessage that is broadcasted when the Event begins for the first time via JSON text
  • the eventEndMessage that is broadcasted when the Event ends via JSON text
  • the eventLoginMessage that is broadcasted when a player logs in while the Event is active via JSON text
  • the eventDisplayMessage that is shown on the EventBlock whenever an event is active via JSON text
  • the eventEnabledMessage that is broadcasted when the event is activated through Crystal Submission via JSON text
  • the eventDuration specified in ticks
  • the crystalSubmission value specified through true/false
  • the minCrystalsSubmitted requirement, when this event is activated, this is the lowest the Crystal submission goal can be.
  • the maxCrystalsSubmitted requirement, when this event is activated, this is the highest the Crystal submission goal can be.
  • the weight number, that defines the weight of the event to be chosen between all other event weights

• Note: Within the .dat file for the active event, only the index of the Event is stored alongside the requiredCrystals/submittedCrystals, implying that if another EventEntry is added that changes the order of previous events, it may impact the active event, however this also means that active events can be tweaked without needing to restart the given event.

• Within the JSON text, following variables can be used to specify certain attributes of the event.

  • totalEventDurationTicks -> The starting duration of the given Event in ticks
  • totalEventDurationSeconds -> The starting duration of the given Event in seconds
  • totalEventDurationMinutes -> The starting duration of the given Event in minutes
  • totalEventDurationHours -> The starting duration of the given Event in hours
  • totalEventDurationDays -> The starting duration of the given Event in days
  • eventId -> The Event ID
  • crystalSubmission -> Whether the event is a CrystalSubmission Event or not.
  • minCrystalsSubmitted -> The lowest the Crystal submission goal can be of the given Event.
  • maxCrystalsSubmitted -> The highest the Crystal submission goal can be of the given Event.
  • eventDurationTicks -> The total remaining ticks of the active event
  • eventDurationSeconds -> The total remaining seconds of the active event
  • eventDurationMinutes -> The total remaining minutes of the active event
  • eventDurationHours -> The total remaining hours of the active event
  • eventDurationDays -> The total remaining days of the active event
  • requiredCrystals -> The total required crystals to be submitted for the event.
  • submittedCrystals -> The total submitted crystals for the event so far.

• To use the given variables, specify the variable name and surround it within braces, e.g {totalEventDurationTicks} within a text field.

• Attached alongside the JAR file is an example config, which is also generated upon launching the game while the given EventConfig is not present.

sure was a lot
Full Changelog: v1.3.0...v1.4.0