Underkeep Priest Aura: Activation & Voidcaller Help

Use the documented demo activation procedure

The developer's reply addresses a specific problem with activating an aura in the demo. Its instruction is to enter the character's Skills section, select the aura and use Activate. That gives you a concrete menu path rather than requiring a guessed shortcut or an assumed automatic activation.

Follow the procedure for the character whose aura you intend to use. Check the selected ability before applying the activation action. If you are comparing the result with an old discussion, keep the historical demo context attached to the comparison instead of treating the reply as a universal current-interface specification.

Understand why the search term says Priest

The collected material spans development and launch, so it contains terminology from different periods. The historical aura question uses Priest, while launch-era guidance associates healing and auras with Voidcaller. Reading those labels in context prevents the old question from creating a fictitious extra class in a release-game roster.

Use the class name shown in your own version when looking through its abilities. If you are following the old activation answer, focus on the aura function and the documented Skills interaction. A terminology change does not justify assigning every older skill description or balance value to the current class unchanged.

Separate learning an aura from activating it

The historical discussion gives an explicit activation action, which is important when a player expects an available aura to be doing something already. The answer is not simply to assume that finding or selecting an ability completes every required interaction. It points to the Skills interface and a named Activate control.

When checking the problem, identify the part that is unresolved. Being able to see an aura, selecting it and applying the documented action are different observations. Describing the exact point at which your experience differs makes the issue easier to compare with the developer's answer.

Treat auras as part of the support role

The official class-development material includes party-wide passive auras in its description of class roles. Launch-era guidance associates aura and healing functions with Voidcaller. Together, those references explain why the ability matters to the party rather than only to an individual character's damage plan.

When planning the group, think about what the support role contributes alongside the frontline and other casters. An aura question can therefore belong to party setup as well as menu troubleshooting. Keep the functional role separate from an invented numerical bonus or a claim that one aura is best in every encounter.

Check the version before applying an old workaround

The activation reply concerns the historical demo, and later updates changed controls and other parts of that product. A workaround can accurately explain an earlier problem without being a required step in every later build. This is why a version label belongs next to the instruction rather than being hidden at the end of a long guide.

If your current interface behaves differently, describe the observed behavior rather than forcing the old wording to fit. Include whether you are playing the demo or full release and the build when asking for help. That keeps a current control question from being answered entirely with assumptions about an older interface.

Keep controller naming advice separate from aura inputs

The developer FAQ documents a controller procedure for entering hero names through Steam Big Picture. That answer concerns text entry and does not provide a current all-controller aura-switching sequence. A verified button for one menu should not be reused as an untested answer for a different ability interface.

For an aura problem on a gamepad, identify the class, menu and labels visible in your version. Compare the actual selection and activation behavior with the historical Skills instruction. This produces a specific troubleshooting question without translating a mouse-era answer into invented buttons for every device.

Do not build a release strategy around old stacking claims

The research explicitly separates the documented activation procedure from old discussions about aura stacking. The reliable instruction is the developer's menu workaround, not a numerical exploit copied into a current build. A historical interaction report should not be promoted into a guaranteed release-game strategy.

Evaluate the ability through the description and behavior presented in your current game. When comparing support options, focus on their documented role in the party. This avoids making a class recommendation depend on an unverified stacking rule or a bonus whose current value has not been established.

Describe the problem before changing the party

An activation difficulty does not by itself show that the support role is unsuitable for your party. First determine whether the issue is terminology, selection, activation or an observation from another version. Those are different problems and do not all call for replacing the adventurer.

Work through the documented menu path before interpreting a historical complaint as a balance conclusion. If you report the issue, include what you selected and what happened after the activation action. That makes it possible to discuss the ability itself rather than guessing which class or interface you meant.

A concise aura checklist

When comparing two aura descriptions, first determine whether they refer to the same class terminology and build. A historical Priest menu instruction and launch-era Voidcaller advice can be related without describing the same interface or current numerical effect. Matching the role is helpful, but matching the exact product and observed action is what makes troubleshooting precise.

Record the ability you selected and the action the interface offered rather than reducing the report to a broad claim that the aura is broken. A description of what happened after using Activate is more useful than an assumption about a missing passive bonus. It also lets another player discuss the documented workaround without importing an old stacking exploit or guessing a button sequence for your controller.

For the historical demo, open Skills, select the aura and press Activate. For launch-era class discussions, recognize Voidcaller as the name associated with healing and auras. For a current interface question, match the product and build before applying an old workaround.

These checks preserve the useful developer answer without inventing an extra class, numerical bonus or controller sequence. They also keep activation separate from broader party recommendations. Once the menu interaction is resolved, use the class and party guides to decide how the support role fits the rest of your four-adventurer group.

Related guides