Skip to content

1.2.0-rc.3

Pre-release
Pre-release
Compare
Choose a tag to compare
@LordMidas LordMidas released this 20 Feb 17:02
· 136 commits to main since this release
1.2.0-rc.3
683dba2

CHANGES

  • add: set the AIBehaviorID of vanilla skills to vanilla behavior during create. This ensures that adding a vanilla skill to an entity will automatically give the AI behavior of that skill to that entity. (#282)
  • change: the serde flag of settings to be ModSetting. instead of MS..This means settings in rc.1 and rc.2 will not be loaded with rc.3 (#283)
  • change: removed requireSettingValue function for now. (#285)
  • change: BB objects are no longer serialized & deserialized using ::Mod.Serialization.serialize and ::Mod.Serialization.deserialize, THIS WILL BREAK MODS written for rc.1 and rc.2. Now, you have to pass a Serialization or Deserialization emulator to their onSerialize or onDeserialize function respectively (#280)

FIXES

  • fix: bug in getBehaviorScriptFromID causing automatic addition of skill behaviors to not work (41c403a)
  • fix: item type names being slightly off in which item type they point to (#277)
  • fix: handling for itemType having a value of 0 for item type name (#277)
  • fix: remove leftover Timer in array_setting.js (3ee3d62)
  • fix: skills adding their behavior to player characters (4b93065)
  • fix: change hook on asset_manager from hookNewObjectOnce to hookNewObject otherwise quitting to the main menu and loading back into the game caused errors. (f18971b)
  • fix: modsettings not being synced between frontend and backend (2ef065b)
  • fix: remove check for existing behavior when adding behavior via AIBehaviorID in skills. Otherwise it was causing some behaviors to be removed mid-execution when the skill removed itself during the behavior execution. (#288)
  • fix: issues with the flag based serialization system (#280)
    • serialization of BB objects is now handled by passing a Serialization or Deserialization Emulator to them.
    • Normal deserialiation now requires a default value.
    • SerDeEmulators are now permanently linked to a FlagContainer they are assigned during instantiation
    • SerializationEmulators now have an Incremental mode where they store their data in the flag container as soon as something is written to them.
    • DeserializationEmulators now immediately clear flags from their FlagContainer as they deserialize.
    • SerDeEmulator flag IDs are validated to make sure they do not collide with flags generated by other emulators.
Assets 3
Loading