Por favor, desactiva tu adblock para ayudarnos a mantener el sitio. ¡Gracias!
Si inicias sesión con tu cuenta de Twitch y estas suscrito no verás estos anuncios.
¡Revisa los ítems del Mercado Negro desde tu casa!
Pixpo
17 de diciembre de 2025
Retail, Midnight, Blizzard, Noticias Blizzard, NoticiasEn una reciente actualización en el Discord de desarrolladores de WoW UI, Blizzard compartió sus nuevos planes respecto a las restricciones de la API de los addons del juego, permitiendo a los jugadores tener mas control sobre las barras de lanzamiento, la sanación en los marcos de unidad y la inclusion de algunos hechizos en una lista blanca.
Aunque muchos de los aspectos técnicos solamente son relevantes para estos desarrolladores, en resumen, Blizzard está flexibilizando algunas restricciones y permitirá a los jugadores mas herramientas para interactuar con las barras de lanzamiento y predecir la sanación y absorción en los marcos de unidad. De forma general, estos cambios surgidos por petición de los jugadores han sido muy positivos.
Uno de los cambios mas importantes es la inclusión de algunos hechizos específicos en la lista blanca, lo que permite a los complementos acceder a sus estados, cargas o tiempos de reutilización. Una gran parte de esto consiste en hacer visible datos como por ejemplo el numero de resurrecciones en combate disponibles. También ha sido añadido el Vuelo Dinámico para poder ver cuantas cargas y habilidades están disponibles.
Ninguno de estos añadidos tiene demasiadas implicaciones directas en el combate, aunque la “gran sorpresa” ha sido añadir tanto del Chamán Mejora como del Cazador de Demonios Devorador, unos recursos muy importantes que carecen de elementos nativos en la interfaz. Si bien incluirlos es una gran mejora para esas especializaciones, esto también contradice la intención de Blizzard de evitar que los addons puedan suponer una ventaja en el juego. Si bien no debemos esperar que esto se extienda a todas las clases, especializaciones o hechizos, parece ser que Blizzard ha mostrado su disposición a evaluar este tipo de necesidades caso por caso. Os dejamos por aquí el comunicado oficial (en inglés) por si queréis echarle un vistazo.
via WoWUIDev Discord said:
Blizzard again! Below you will find a list of changes we are making to addon restriction APIs in the coming weeks.
These are not the entirety of the changes we are planning, just the ones already committed to for the immediately upcoming Beta releases.
NOTE: Beta 5 will be the last Beta build we put out this year. We will be continuing to work on addon dev requests until the holidays but Beta 6 won't be made until January.
Also note that Beta 4 had more changes than expected, and Beta 5 has fewer due to build timing (Beta 4 ended up being built later than expected).
REMINDER: Beta builds have switched to a 12.0.1 version number instead of 12.0.0. This is because 12.0.0 will be the version used for Midnight pre-patch, and 12.0.1 will be the version used for actual Midnight launch. The remainder of Beta will feature 12.0.1 builds, while PTR (when it goes up) will feature 12.0.0 builds. We will continue to make addon-related changes in 12.0.0 until we make our pre-patch Release Candidate (RC) build.
One important thing to note here is that we DO plan to have these new addon restrictions active in pre-patch (12.0.0), rather than waiting until 12.0.1. The reason for this is we want to give players a chance to get used to the new addon landscape prior to Midnight launch. We are not in 12.0.0 RC yet, so you can continue to test in Beta for now, but once we pick an RC build (we will let you know when that happens) we advise addon authors looking to prepare for pre-patch switch to testing on PTR instead of Beta.
After the 12.0.0 RC is chosen, our engineers will be switching over to making most addon-related changes in 12.0.1 (outside of very high priority stuff). We will continue to make changes to 12.0.1 all the way up until launch (and well past launch even, in follow-up patches) to provide you with more of the QoL changes you have requested.
We have added a new UnitHealPredictionCalculator Lua object (created via a new CreateUnitHealPredictionCalculator API), and an associated API UnitGetDetailedHealPrediction that accepts this object type.
Addons can use these APIs to calculate all of the heal prediction and absorb data needed for passing directly into other APIs.
This object provides various options, such as allowing for damage absorbs to be clamped to either missing health, missing health after adding incoming healing, or maximum health.
Pixpo17 de diciembre de 2025Retail, Midnight, Blizzard, Noticias Blizzard, NoticiasVery brief example shown below:
local calculator = CreateUnitHealPredictionCalculator();
UnitGetDetailedHealPrediction(unit, unitDoingTheHealing, calculator); -- 'calculator' is updated with new data after this call.
local incomingHeals, incomingHealsFromHealer, incomingHealsFromOthers, incomingHealsClamped = calculator:GetIncomingHeals();
myStatusBar:SetValue(incomingHealsFromHealer);Added a new optional direction parameter to StatusBar:SetTimerDuration that allows the status bar to calculate its fill from remaining duration rather than elapsed (for channeled spells primarily).
Added a new PARTY_KILL event that gets sent when a party member kills a unit. The payload is 2 unitGUIDs, the attacker and target. Both are secret when the associated unit's identity is secret.
Adding numerous spells to the whitelists for cooldown/aura secrecy: Skyriding spells, the GCD spell, Maelstrom Weapon, Devourer DH resource spells, Combat Res spells.
Continue to call out spells that you think should be whitelisted, we will evaluate each of them individually.
We are removing several APIs (in C_UnitAuras, C_Spell and C_ActionBar) that are no longer needed now that Duration objects are a thing.
We are adding 2 new APIs (C_CurveUtil.EvaluateColorFromBoolean and C_CurveUtil.EvaluateColorValueFromBoolean) that can be used to convert a secret boolean to a color.
This is in preference to adding SetStatusBarColorFromBoolean, SetColorTextureFromBoolean, etc.
We are adding a new castbar spell sequence ID delivered with spellcast events and from the UnitCastingInfo/UnitChannelInfo APIs. This sequence ID is only delivered for casting events that should display a castbar in the UI, is incremented on each new spellcast, and is never secret.
We will be removing secret restrictions on several values needed by addons to properly display enemy empowered casts (number of stages and the percentage of cast time each stage consumes).
We will be adding a way to include the hold-at-max time of empowered casts in a duration object.
We are adding a new SecondsFormatter Lua object that will allow addons to format secret time values into strings.
Other numeric formatting solutions are also being worked on, including a solution for formatting differences between cast durations (eg. for spell pushback).
Several functions (strsplit, strjoin, strconcat) that got mistakenly removed from the restricted environment are being added back.
We are fixing an issue where secret values are made non-secret following a UI reload.