CopperCube REAPER behavior/action

ALL HADOKEN RECORDS COPPERCUBE EXTENSIONS:

https://hadoken-records.itch.io/

If you no longer need an object in your running scene and want to get rid of it, deleting objects at runtime in the CopperCube 3d game engine can often be tricky. To avoid crashes or complicated variable configurations, CopperCube REAPER comes in handy to remove your scene nodes from the game without hassle, saving processing power and ensuring scene performance.

Use case example:

"... Imagine you have an enemy AI with its enemy AI behavior. Then you clone the enemy at runtime. Multiple clones will bear the exact enemy AI behavior of the original one. Then things can get difficult for telling which of the clones should be taken out of the game when having zero health. To keep track which one has to be deleted, it can easily be done from within the enemy AI behavior script. But when a scene node decides to delete itself CoppetCube in most cases crashes. Deleting nodes must be executed from another node to prevent those kind of crashes. Now the REAPER extension comes in - giving a scene node the possibility to send itself from its own script to death and be deleted. That would not be possible with CopperCube's built-in delete scene node only ..."

Installation:

Unzip and put both extension files "behavior_HadokenCopperCubeREAPER.js" and "action_HadokenSend2REAPER.js" into your CopperCube extensions folder & restart CopperCube to make them available.

HowTo use:

Step 1:

put a node with "behavior_HadokenCopperCubeREAPER" in your scene which will permanently watch as REAPER over nodes to be taken permanently out of the game

Step 2:

initiate removal of your scene nodes by executing the action "action_HadokenSend2REAPER"

Please check the provided demo scene "HadokenCopperCubeREAPER_2023-02-17_Demo.ccb" to see how these simple steps work.

Find CopperCube & further general extension documentation under: https://ambiera.com/coppercube/index.html