Collectibles Part 3

This short lesson adds a visual burst and sound to the existing coin pickup. The coin’s removal behavior comes from Part 1, and the character’s count comes from Part 2. Here the focus is feedback at the collected Actor’s location.

The example uses the recording’s Starter Content emitter and sound assets. The exact engine release is unidentified; this is not a demonstration of authoring a new effect or converting it to another particle system.

Use the coin’s position for both feedback operations

At 00:01–02:03, the Coin Blueprint receives Spawn Emitter at Location and Play Sound at Location operations. Get Actor Location targets the coin itself, and its returned position supplies the location for both operations.

This ties the feedback to the collected instance. Several coins can share the Blueprint while producing effects at different positions in the level, without a separate hard-coded location for each one.

The source extends the existing pickup event, but does not read out every execution pin around the earlier Destroy Actor operation. Inspect that sequence so both feedback operations execute with the intended coin location available. The particle and sound nodes require execution as well as location data; connecting the vector alone does not trigger them.

Replace the persistent sparks with a suitable burst

During 02:03–03:01, the first play test uses sparks and a related sound. The instructor rejects the effect because the sparks persist much longer than desired for this pickup response.

The effect is changed to a Starter Content explosion, with an explosion sound selected to accompany it. The correction is an asset choice based on the observed result. The recording does not reconfigure the original sparks’ lifetime or implement a general cleanup system for looping effects.

Test the duration as well as whether an effect appears. A pickup can trigger feedback correctly while using an asset whose looping or persistence makes it unsuitable for a brief collection event.

Confirm that feedback follows each collected instance

At 03:01–03:38, the final test produces the explosion and sound when a collectible is reached, at the location of that pickup. This confirms the intended positional association in the example scene.

The existing count and removal behavior remain separate concerns. Check that the added feedback does not obscure whether the coin was removed and counted, but do not infer new inventory behavior from the effect itself.

Sound attenuation, concurrency, multiplayer replication, and performance under many simultaneous pickups are not evaluated here. The completed result is local pickup feedback using the selected existing assets.