AdvancedWidgetEase

Popup menus, pause panels and HUD strips usually arrive on screen with a cut. AdvancedWidgetEase exists to replace that cut with motion — tween actions that carry a widget from one state to another instead of letting it appear and vanish instantly. The scenes it serves are the ordinary ones in a menu build: a shop panel that slides and fades in, a button that scales under the cursor, a tooltip that eases into place beside its icon, a status label that shifts color when something changes.

Eight widget properties can be tweened. Six are named directly — move, scale, rotate, color, opacity and bezier — which covers the parts of a widget that most transitions actually touch: where it sits, how large it is, what angle it holds, what tint it carries, how transparent it is, and how it travels along a curve rather than a straight line. Any tween action can be assembled from those properties, so one transition is free to combine several of them at once instead of animating a single value in isolation.

Move, Scale, Rotate, Color, Opacity, Bezier

Each property answers a different question during a transition. Move governs position, which is what makes an off-screen panel slide into frame. Scale governs size, useful for a press response or for a panel that grows from a small origin point. Rotate governs angle, and it is one of the properties called out in the asset's own tags alongside Transform and Scale, which suggests rotation is treated as a first-class part of the set rather than an afterthought.

Color and opacity work on appearance rather than placement. Color lets a widget's tint change over the duration of a tween, which reads well for state feedback — a highlighted row, a warning label, a button settling into its active look. Opacity handles fade, the cheapest way to soften an entrance or exit without moving anything. Bezier covers curved motion, so a widget can follow a path that bends instead of tracking a straight line between two points.

The combination is where the tool does its real work. A panel that fades while it slides, a button that scales and rotates together, a notification that follows a bezier path while its color shifts — all of these are built from the same small property set, driven by the same tween action system.

Thirty-Five Ease Functions

Timing decisions are handled by 35 tween ease functions. That count matters in a practical way: an ease curve is what separates a mechanical linear slide from a movement that starts quickly and settles, or one that hesitates and then releases. With 35 to choose from, the same move or scale tween can read as snappy, soft, weighty or abrupt depending on which curve drives it.

The purpose stated for the ease set is straightforward — making an action more vivid. In a menu context that translates to transitions with a bit of character rather than uniform interpolation. Because the easing library is shared across all eight properties, a designer can keep a consistent motion personality across an entire interface: the same curve family applied to a panel's move, a button's scale and a label's opacity keeps the screen feeling like one system instead of a collection of separately tuned pieces.

Testing Actions Inside the Project

An example is included in the project so the tween actions can be tried out directly. That is a practical arrangement for this kind of tool. Ease curves are hard to judge from a list of names or a numeric description — the difference between two similar-looking functions only becomes obvious when a widget is actually moving on screen. Having the example inside the project means each action can be triggered and watched, and the curve that fits a particular panel can be picked by eye rather than by guesswork.

Working from an existing example also shortens the gap between trying something and shipping it. Once a transition reads correctly in the example, the same action setup carries over to the real menu widgets.

Blueprint, Code and the Rest of the Tag Set

The asset is tagged with Design, Rotate, Scale, Project, Maple, Transform, Blueprint and Code. Read together, that describes a tool that sits in the interface and implementation layer rather than the modeling pipeline — it is about transforming widgets in real time, wired up through Blueprint and backed by code. Widget motion set up in Blueprint is useful precisely because menus change often: a transition can be adjusted without a rebuild of the surrounding systems.

Compatibility is noted for SpherePopupMenu, which places the tool neatly alongside popup menu work — the exact context where slide, fade and scale transitions are most visible to a player. Popup panels are also where a bad transition is most noticeable, since they occupy a large share of the screen and appear repeatedly. Tweening those panels with a considered ease curve makes the difference between a menu that feels assembled and one that feels authored.

Where It Belongs in a Menu Build

AdvancedWidgetEase is aimed at teams already building their interface in Blueprint who want motion without hand-authoring each transition. Reach for it when a popup menu needs to enter and exit with a slide, fade or scale; when a button needs a press response; when a panel needs curved travel rather than a straight-line hop. The eight properties and 35 ease functions cover the ordinary vocabulary of interface motion, and the bundled example provides the space to settle on the right curve before the transition goes into the shipping screen.

Explore Similar Assets

• Daily Life AI
• Breakdown
• Procedural Turn in Place System
• Smart Locomotion
• Kai Locomotion System