jVars

2026.04.18.21.35.03 (2026-04-19)

Full Changelog Previous Releases

• Corrected two major issues:
  1. If an external app alters cvars which this app manages, we were not recording the changed value in the persistence to hand off during the next reload, thereby ensuring it makes it into our app system. The app was only updating the Dictionary.CurrentValue. From here on, if an external(other than jvars) app updates CVars, those changes should be persisted to jvars. i ran a couple test to check this was happening.
  2. SetCVar and C_CVar.SetCVar are both returning nil when users make changes in jvars. Because of this nil issue, jvars was not cascading during real-time changes/while the app is open. the cascades were confirmed to only be happening during subsequent reloads. This behavior was corrected so that it happens during both events.
     Both issues were uncovered during an investigation around why UnitNameOwn updates were not disabling the player nameplate when toggled off. This was because of a cascading update which was not firing during real-time changes within jvars. This was compounded by the fact that the external/in-game method for turning off player nameplates was not reciprocating the change back to the jvars database.