No puedo utilizar a mi compañero al hacer un abismo, lo cual me hace imposible prácticamente jugar abismos

Soporte Soporte técnico
1

Buenas, recientemente la semana pasada haciendo contenido de abismos del nuevo parche, de un momento a otro mi compañero dejo de funcionar, directamente no hace nada en el abismo, y no puedo cambiar ninguna de sus configuraciones, esta reseteado de 0. Esto me ocurre en mi main “Maspy-Illidan” y en los demas personajes funciona bien, probe miles de posibles soluciones que ayudaron a gente con problemas similares pero nada funciona, envie varios tickets y todos me respondieron que no podian hacer nada y que hiciera un post aca. Tambien estuve indagando en el problema para puntualizarlo con ayuda de chatgpt y la respuesta a la que llegamos despues de probar varios comandos es esta:

Character-specific Delve companion profile corruption

Affected character is level 90, has completed the Midnight Delve introduction and has Tier 11 unlocked.

Valeera appears in Delves but has no selectable role and her abilities cannot be configured.

API comparison:

Working character:
C_DelvesUI.GetCompanionInfoForActivePlayer() = 12
C_DelvesUI.GetPlayerCompanionPDEID() = 396

Affected character:
C_DelvesUI.GetCompanionInfoForActivePlayer() = 0
C_DelvesUI.GetPlayerCompanionPDEID() = nil / empty result

Blizzard_DelvesCompanionConfiguration also returns:
companionFactionID = 0
companionLevel = 0
companionRepInfo = nil
selectionNodeID = 0

Opening the companion configuration generates:
bad argument #1 to C_Traits.GetNodeInfo(configID, nodeID)
and
attempt to index local ‘companionRepInfo’ (a nil value)

Other characters on the same account work correctly.

Please investigate/reset this character’s Delve profile / companion state.

Por favor les pido que hagan algo al respecto, ya que no puedo jugar abismos con mi main.

2

Creo que estas cosas deberian ser tomadas mas en cuenta y que deberian dar mejores respuestas y soluciones estoy contigo ¡Maspy!

3

BTW a mi me pasa lo mismo

4

Pucha mano, te leo y me da una mezcla de alivio y cólera brava, pensé que era el único con esta vaina. En mi caso no me pasó solo en el main, se me rompieron tres personajes con exactamente el mismo error.

Los Abismos son de lejos mi contenido favorito de todo el juego, es prácticamente a lo único que le meto vicio parejo, y tener que ver a Valeera ahí parada de adorno, como si estuviera pintada, sin poder moverle ni un mísero rol y botando errores de Lua como si esto fuera un server pirata del 2008, de verdad te quita todas las ganas de loguear. Una belleza pagar la suscripción puntual para farmear puro aire y bugs.

Apoyo a Maspy!

5

Pude solucionar esto despues de horas indagando con chat gpt, dejo el resumen de mi problema y mi solucion por si alguien lo necesitara en el futuro.

Valeera Delve Companion completely bugged on one character — workaround that actually fixed it

I had a character where Valeera was completely broken:

  • No role selected

  • Could not change role

  • Could not change Combat/Utility Curios

  • Companion configuration UI threw Lua errors

  • Other characters on the same account worked normally

The usual fixes did nothing: relogging, /reload, changing Delves/Tiers, disabling addons, opening Journeys, using another character, campaign/intro checks, etc.

How I confirmed the character was bugged

Run:

/dump C_DelvesUI.GetCompanionInfoForActivePlayer()

and:

/dump C_DelvesUI.GetPlayerCompanionPDEID()

On my broken character:

GetCompanionInfoForActivePlayer() = 0
GetPlayerCompanionPDEID() = nil / empty result

On a working character:

GetCompanionInfoForActivePlayer() = 12
GetPlayerCompanionPDEID() = 396

The broken character still had Valeera’s actual trait tree:

Faction = 2744
Tree = 1223
Role node = 110817
Combat node = 110786
Utility node = 110785

So the tree itself wasn’t gone — the active companion state seemed to be desynced.

The fix

1. On a WORKING character

Get the EntryID of the currently selected Valeera role:

/dump C_Traits.GetNodeInfo(C_Traits.GetConfigIDByTreeID(1223),110817).activeEntry.entryID

Save the number it returns.

Example:

123456

Do not copy my example number. Use the number your own character returns.

2. Log onto the BROKEN character

Go inside a Delve, preferably next to Valeera’s Companion Supplies and out of combat.

Replace XXXXX below with the EntryID you got from the working character:

/run local c=C_Traits.GetConfigIDByTreeID(1223);local s=C_Traits.SetSelection(c,110817,XXXXX);print("Set:",s,"Ready:",C_Traits.IsReadyForCommit());if s and C_Traits.IsReadyForCommit() then print("Commit:",C_Traits.CommitConfig(c)) end

In my case, SetSelection worked and the config committed successfully.

3. Leave the Delve and enter again

This was the important part.

After leaving and re-entering the Delve, Valeera suddenly worked normally again.

The Companion UI opened without errors, the role and Curios could be changed normally, and these commands now returned:

GetCompanionInfoForActivePlayer() = 12
GetPlayerCompanionPDEID() = 396

I then tested:

  • Changing Valeera’s role normally

  • Changing both Curios normally

  • Closing/reopening the Valeera UI

  • Leaving/re-entering Delves

  • Relogging

  • Switching to another character and back

Everything continued working.

So this appears to have fully repaired the character, not just temporarily bypassed the UI.

Important

Do not hardcode another player’s ConfigID. Get yours dynamically with:

C_Traits.GetConfigIDByTreeID(1223)

The ConfigID is character-specific.

The relevant Valeera nodes in my client were:

Tree = 1223
Role = 110817
Combat = 110786
Utility = 110785

If your symptoms are specifically:

GetCompanionInfoForActivePlayer() = 0
GetPlayerCompanionPDEID() = nil

while another character returns 12 / 396, this workaround may be worth trying.

This fixed a character that none of the normal Valeera/Delve workarounds could repair.