<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Cluster Official on Medium]]></title>
        <description><![CDATA[Stories by Cluster Official on Medium]]></description>
        <link>https://medium.com/@cluster_official?source=rss-29c6ed8c5a84------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WW4OsJYF4iYUU988-i5JJw.png</url>
            <title>Stories by Cluster Official on Medium</title>
            <link>https://medium.com/@cluster_official?source=rss-29c6ed8c5a84------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 17:52:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cluster_official/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[[Beta Feature] Using setPostProcessEffects to implement time-of-day visual changes]]></title>
            <link>https://medium.com/@cluster_official/beta-feature-using-setpostprocesseffects-to-implement-time-of-day-visual-changes-217237710221?source=rss-29c6ed8c5a84------2</link>
            <guid isPermaLink="false">https://medium.com/p/217237710221</guid>
            <dc:creator><![CDATA[Cluster Official]]></dc:creator>
            <pubDate>Tue, 28 Jul 2026 13:22:45 GMT</pubDate>
            <atom:updated>2026-07-28T13:22:45.926Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*75Q_PNQkMcyu_Vh0mEV-GA.png" /></figure><p>This article explains the use of a <strong>Beta feature</strong> of the Cluster Creator Kit.</p><p><strong>Beta features</strong> are features that have not yet reached official release status. Due to this, they may behave unpredictably or see changes in future updates. While the feature is in beta as of the writing of this article, it may have been officially released by the time you read this, so we recommend checking the <a href="https://docs.cluster.mu/script/en/">Script Reference</a> when making use of the information in this article.</p><p>To make use of Beta features, you need to upload your world with the “Enable beta features” setting set to On in the Cluster Creator Kit. Likewise, when creating worlds with the World Craft feature, you will need to set the “Enable beta” setting to On when creating a Craftspace. See the <a href="https://docs.cluster.mu/creatorkit/en/installation/beta/">documentation page on Beta features</a> for details.</p><p>The <a href="https://docs.cluster.mu/script/en/classes/PlayerHandle.html#setpostprocesseffects">PlayerHandle.setPostProcessEffects</a> API enables you to add visual post-processing effects to players within your world. This guide will demonstrate its use by implementing dynamic time-of-day visual changes that take effect on players in the vicinity of an item.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zd4VzOOndQW-rIZBlfOTZg.png" /></figure><h3><strong>Sample code</strong></h3><p>Below is the script we will be using in this example.<br>Add a <a href="https://docs.cluster.mu/creatorkit/en/item-components/scriptable-item/">Scriptable Item</a> component to either a GameObject residing in the world, or an item intended to be uploaded as a Craft Item. Paste the below script into the Source Code of the Scriptable Item.</p><p>The World or Craft Item will also need to be uploaded with the “Enable beta” settings turned On.</p><pre>const morningHour = 6;<br>const dayHour = 11;<br>const eveningHour = 19;<br>const nightHour = 22;<br><br><br>const setPostProcessEffectsInterval = 0.1;<br>const getPlayersNearDistance = 30;<br><br><br>function getMorningEffects() {<br>    let effects = new PostProcessEffects();<br>    effects.bloom.active = true;<br>    effects.bloom.threshold.setValue(0.0);<br>    effects.bloom.intensity.setValue(1.0);<br><br><br>    return effects;<br>};<br><br><br>function getDayEffects() {<br>    return null;<br>};<br><br><br>function getEveningEffects() {<br>    let effects = new PostProcessEffects();<br>    effects.bloom.active = true;<br>    effects.bloom.threshold.setValue(0.5);<br>    effects.bloom.intensity.setValue(0.8);<br>    effects.colorGrading.active = true;<br>    effects.colorGrading.colorFilter.setValue(1.0, 0.5, 0.3, 1);<br><br><br>    return effects;<br>};<br><br><br>function getNightEffects() {<br>    let effects = new PostProcessEffects();<br>    effects.bloom.active = true;<br>    effects.bloom.threshold.setValue(1.0);<br>    effects.bloom.intensity.setValue(2.0);<br>    effects.colorGrading.active = true;<br>    effects.colorGrading.colorFilter.setValue(0.3, 0.3, 0.3, 1);<br><br><br>    return effects;<br>};<br><br><br>function getJSTDate() {<br>    const date = new Date();<br> <br>    // Convert the date to Etc/GMT-9 (+9 hours difference)<br>    date.setTime(date.getTime() + 3600000 * 9);<br> <br>    return {<br>        timezone: &quot;Etc/GMT-9&quot;,<br>        hours: date.getUTCHours(),<br>        minutes: date.getUTCMinutes(),<br>        seconds: date.getUTCSeconds(),<br>    };<br>};<br><br><br>$.onStart(() =&gt; {<br>    $.state.queue = [];<br>    $.state.waitingTime = 0;<br>});<br><br><br>$.onUpdate((deltaTime) =&gt; {<br>    let waitingTime = $.state.waitingTime - deltaTime;<br>    if (waitingTime &lt;= 0) {<br>        let hours = getJSTDate().hours;<br><br><br>        let effects = null;<br>        if (hours &lt; morningHour) effects = getNightEffects();<br>        else if (hours &lt; dayHour) effects = getMorningEffects();<br>        else if (hours &lt; eveningHour) effects = getDayEffects();<br>        else if (hours &lt; nightHour) effects = getEveningEffects();<br>        else effects = getNightEffects();<br><br><br>        let queue = $.state.queue;<br><br><br>        if (queue.length === 0) {<br>            queue = $.getPlayersNear($.getPosition(), getPlayersNearDistance);<br>        }<br><br><br>        let player = queue.shift();<br>        if (player) player.setPostProcessEffects(effects);<br><br><br>        $.state.queue = queue;<br><br><br>        waitingTime = setPostProcessEffectsInterval;<br>    }<br>    $.state.waitingTime = waitingTime;<br>});</pre><p>By placing an item containing this script into the world, players in the vicinity of the item will see different post-processing effects depending on the current time (Japan Standard Time), namely morning, daytime, evening, and nighttime.</p><p>In this example, players within 30 meters of the item are affected.</p><h3><strong>Sample code, explained</strong></h3><h4><strong>Morning effect</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*VuTb2Ab9xxVxKb08se5yAg.jpeg" /></figure><pre>function getMorningEffects() {<br>    let effects = new PostProcessEffects();<br>    effects.bloom.active = true;<br>    effects.bloom.threshold.setValue(0.0);<br>    effects.bloom.intensity.setValue(1.0);<br><br><br>    return effects;<br>};</pre><p>This function sets the effect parameters for the morning time period. The brightness of the morning sun is expressed through the <a href="https://docs.cluster.mu/script/en/interfaces/BloomSettings.html">Bloom</a> effect.</p><p>For details on each parameter, refer to the <a href="https://docs.cluster.mu/script/en/classes/PostProcessEffects.html">Script Reference</a>.</p><h4><strong>Daytime effect</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*cU5MReN3v5DXqh7avr1ylw.jpeg" /></figure><pre>function getDayEffects() {<br>    return null;<br>};</pre><p>This function sets the effects for the daytime period. We want to keep the standard appearance and avoid using any effects for the daytime, so we return <strong>null </strong>to reset all effects.</p><h4><strong>Evening effect</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*mPv6XGDyrALb-knjlzJXFQ.jpeg" /></figure><pre>function getEveningEffects() {<br>    let effects = new PostProcessEffects();<br>    effects.bloom.active = true;<br>    effects.bloom.threshold.setValue(0.5);<br>    effects.bloom.intensity.setValue(0.8);<br>    effects.colorGrading.active = true;<br>    effects.colorGrading.colorFilter.setValue(1.0, 0.5, 0.3, 1);<br><br><br>    return effects;<br>};</pre><p>This function sets the effects for the evening period. Alongside the <a href="https://docs.cluster.mu/script/en/interfaces/BloomSettings.html">Bloom</a> effect, the <a href="https://docs.cluster.mu/script/en/interfaces/ColorGradingSettings.html">ColorGrading</a> effect, which modifies the colors of the screen, is also used to simulate the colors of the sunset.</p><h4><strong>Nighttime effect</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*tie69dBke9-7PR0F7TA82w.jpeg" /></figure><pre>function getNightEffects() {<br>    let effects = new PostProcessEffects();<br>    effects.bloom.active = true;<br>    effects.bloom.threshold.setValue(1.0);<br>    effects.bloom.intensity.setValue(2.0);<br>    effects.colorGrading.active = true;<br>    effects.colorGrading.colorFilter.setValue(0.3, 0.3, 0.3, 1);<br><br><br>    return effects;<br>};</pre><p>Finally, this function sets the effects for the nighttime period. We set a threshold to the <a href="https://docs.cluster.mu/script/en/interfaces/BloomSettings.html">Bloom</a> effect to apply it only to areas that are brightly lit. <a href="https://docs.cluster.mu/script/en/interfaces/ColorGradingSettings.html">ColorGrading</a> is also used to darken the overall scene.</p><h4><strong>Obtain the current time</strong></h4><pre>function getJSTDate() {<br>    const date = new Date();<br> <br>    // Convert the date to Etc/GMT-9 (+9 hours difference)<br>    date.setTime(date.getTime() + 3600000 * 9);<br> <br>    return {<br>        timezone: &quot;Etc/GMT-9&quot;,<br>        hours: date.getUTCHours(),<br>        minutes: date.getUTCMinutes(),<br>        seconds: date.getUTCSeconds(),<br>    };<br>};</pre><p>This function obtains the current time in Japan Standard Time.<br>While the time can be obtained from the <strong>Date </strong>object directly, this may be affected by the player’s local time zone. To avoid this, we obtain the Coordinated Universal Time (UTC) first, and calculate Japan Standard Time (JST) by adding the time zone offset. (See also: <a href="https://docs.cluster.mu/script/en/index.html#obtaining-the-time-and-a-word-of-warning-on-time-zones">Obtaining the time, and a word of warning on time zones</a>)</p><pre>$.onUpdate((deltaTime) =&gt; {<br>    let waitingTime = $.state.waitingTime - deltaTime;<br>    if (waitingTime &lt;= 0) {<br>        // ...Do stuff... (code omitted, explained below)<br>        waitingTime = setPostProcessEffectsInterval;<br>    }<br>    $.state.waitingTime = waitingTime;<br>});</pre><p>Operations against the <a href="https://docs.cluster.mu/script/en/classes/PlayerHandle.html">PlayerHandle</a>, such as <a href="https://docs.cluster.mu/script/en/classes/PlayerHandle.html#setpostprocesseffects">setPostProcessEffect</a>, have limits on how frequently they can be invoked. Therefore we need to implement a mechanism that waits a while before the operation is invoked again.</p><pre>let hours = getJSTDate().hours;<br><br><br>let effects = null;<br>if (hours &lt; morningHour) effects = getNightEffects();<br>else if (hours &lt; dayHour) effects = getMorningEffects();<br>else if (hours &lt; eveningHour) effects = getDayEffects();<br>else if (hours &lt; nightHour) effects = getEveningEffects();<br>else effects = getNightEffects();</pre><p>We obtain the post-processing effects appropriate for each time period.<br>We take the hour value of the current time (24-hour time), and decide the time period as below:</p><ul><li>0–5: Nighttime</li><li>6–10: Morning</li><li>11–18: Daytime</li><li>19–21: Evening</li><li>and for hours after that, Nighttime again.</li></ul><p>The thresholds for each time period are defined as constants at the beginning of the script. For instance, if we modify the below:</p><pre>const morningHour = 6;</pre><p>to this:</p><pre>const morningHour = 9;</pre><p>The threshold of morningtime will change to 9:00 AM, with 0–8 becoming night, and 9–11 becoming morning.</p><h4><strong>Applying the effects</strong></h4><pre>let queue = $.state.queue;<br><br><br>if (queue.length === 0) {<br>    queue = $.getPlayersNear($.getPosition(), getPlayersNearDistance);<br>}<br><br><br>let player = queue.shift();<br>if (player) player.setPostProcessEffects(effects);<br><br><br>$.state.queue = queue;</pre><p>We obtain the list of players saved in <a href="https://docs.cluster.mu/script/en/interfaces/ClusterScript.html#state">$.state</a>. If it is empty, <a href="https://docs.cluster.mu/script/en/interfaces/ClusterScript.html#getplayersnear">$.getPlayersNear()</a> is used to fetch a list of <a href="https://docs.cluster.mu/script/en/classes/PlayerHandle.html">PlayerHandle</a> objects for players in the nearby area.</p><p><strong>shift() </strong>is a function that returns one item from a list, and also removes that item from the list. Here, we take out a <a href="https://docs.cluster.mu/script/en/classes/PlayerHandle.html">PlayerHandle</a> from the player queue, and apply the <a href="https://docs.cluster.mu/script/en/classes/PostProcessEffects.html">PostProcessEffects</a> on that player.</p><p>The updated player list is then saved back into <a href="https://docs.cluster.mu/script/en/interfaces/ClusterScript.html#state">$.state</a>.</p><p>By fetching a new nearby player list each time the queue empties, we ensure that the effect continuously updates for all players in the vicinity.</p><p>As we have seen, applying post-processing effects with <a href="https://docs.cluster.mu/script/en/classes/PlayerHandle.html#setpostprocesseffects">setPostProcessEffect</a> can dramatically change the overall atmosphere of the player’s view. You can even have the effects react to various in-game events including the time of day, the progression of the game, the player’s remaining hit points, etc.</p><p>From here, you can push things further by scripting more complex conditions and fine-tuning parameters to your liking. Give it a try!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=217237710221" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Material Property Manipulation API: Creating a Craft Item That Randomly Changes Color When…]]></title>
            <link>https://medium.com/@cluster_official/the-material-property-manipulation-api-creating-a-craft-item-that-randomly-changes-color-when-d18324603b60?source=rss-29c6ed8c5a84------2</link>
            <guid isPermaLink="false">https://medium.com/p/d18324603b60</guid>
            <dc:creator><![CDATA[Cluster Official]]></dc:creator>
            <pubDate>Mon, 27 Jul 2026 07:31:50 GMT</pubDate>
            <atom:updated>2026-07-27T07:31:50.019Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7BCONrdo5AJRMqeaoIYmGQ.png" /></figure><h3><strong>The Material Property Manipulation API: Creating a Craft Item That Randomly Changes Color When Clicked</strong></h3><p>You can control the properties of materials by using the Material Property Manipulation API. For example, you can change a material’s color or, by combining them with shaders, move vertices around to create wave-like effects.</p><p>For Craft Items, the API allows you to set values for <strong>baseColor</strong> and <strong>emission</strong>. In worlds built with the Cluster Creator Kit, you can also set values for other shader-exposed properties as well.</p><p>This guide will walk you through a basic example of creating a Craft Item that randomly changes color every time it is clicked, along with sample code.</p><ul><li>Material Property Manipulation API<br>・<a href="https://docs.cluster.mu/script/en/interfaces/ClusterScript.html#material">ClusterScript.material</a><br>・<a href="https://docs.cluster.mu/script/en/interfaces/MaterialHandle.html">MaterialHandle</a><br>・<a href="https://docs.cluster.mu/creatorkit/en/item-components/item-material-set-list/">ItemMaterialSetList </a>Component</li></ul><h3><strong>Basic Configuration</strong></h3><h4><strong>Set up an ItemMaterialSetList component on the object you want to control the material of</strong></h4><p>To start using the Material Property Manipulation API, you first need to set up an <a href="https://docs.cluster.mu/creatorkit/en/item-components/item-material-set-list/"><strong>ItemMaterialSetList </strong></a><strong>component</strong>.</p><p>You can either attach the component to a GameObject that contains a <a href="https://docs.cluster.mu/creatorkit/en/item-components/scriptable-item/">Scriptable Item</a>, or to one of its children, and reference it using SubNode. The “Id” string you assign when configuring <a href="https://docs.cluster.mu/creatorkit/en/item-components/item-material-set-list/">ItemMaterialSetList</a> will be the identifier used to refer to the material from within scripts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IB0L2aFa4uDbyOidnNIyMA.png" /></figure><h4><strong>Sample code: A craft item that randomly changes material color when clicked</strong></h4><p>You can use the <a href="https://docs.cluster.mu/script/en/interfaces/ClusterScript.html#material">material</a> API, recently added to ClusterScript, to obtain the <a href="https://docs.cluster.mu/script/en/interfaces/MaterialHandle.html">MaterialHandle</a> needed to manipulate your target material.</p><p>The below is a code sample for a Craft Item that randomly changes material color when clicked, along with its.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*fgAtMZR-c8s3sepzlZ8-zQ.gif" /></figure><pre>$.onInteract(() =&gt; {<br>  const mat = $.material(&quot;base&quot;);<br>  mat.setBaseColor(Math.random(), Math.random(), Math.random(), 1);<br>});</pre><p>You can also use the <a href="https://docs.cluster.mu/script/en/interfaces/MaterialHandle.html#setemissioncolor">setEmissionColor</a> API to control the <strong>emission</strong> (glow) of the Craft Item’s material. In worlds built using the Cluster Creator Kit, you can have control over more material properties; take a look at the <a href="https://docs.cluster.mu/script/en/interfaces/MaterialHandle.html">MaterialHandle Script Reference page</a> for full details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*MywNXo3v3UcmItkhFdL9YQ.gif" /></figure><p>While outside the scope of this article, combining this API with custom shaders will give you even more freedom in creating complex expressions, such as undulating wave effects. If you’re interested, it’s worth giving it a try!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d18324603b60" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementing a “Lives” (Retries) System in Your Game]]></title>
            <link>https://medium.com/@cluster_official/implementing-a-lives-retries-system-in-your-game-3f887bae229b?source=rss-29c6ed8c5a84------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f887bae229b</guid>
            <dc:creator><![CDATA[Cluster Official]]></dc:creator>
            <pubDate>Tue, 30 Jun 2026 12:08:17 GMT</pubDate>
            <atom:updated>2026-06-30T12:08:17.242Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WNloAqmKl-DDYATYJQ87vg.jpeg" /></figure><p>This guide will show you how to implement the classic “lives” system found in many games. Lives will decrease when the player dies, and reaching zero will trigger a Game Over. We will also save the number of lives so it carries over to the next playthrough.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*cbNJRVutAB5q4lo-NUWjFw.gif" /></figure><h3><strong>Creating a system to manage the lives count</strong></h3><h4><strong>Decrementing lives when the player dies</strong></h4><p>We will first build a system that decrements the number of remaining lives when the player dies, using the <a href="https://docs.cluster.mu/creatorkit/en/operation-components/player-logic/">Player Logic</a> component.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0QaVtf20j5SKXGLtLPVjzQ.png" /></figure><ul><li>Create a new empty GameObject, either by right-clicking the Hierarchy, or going to the GameObject menu in the menu bar and selecting Create Empty. Give it the name “PlayerLives” (without the quotes; the same goes for all further text in quotes).<br>・Click the PlayerLives object to open its Inspector. Select <strong>Add Component</strong>, and add the <a href="https://docs.cluster.mu/creatorkit/en/operation-components/player-timer/">Player Timer</a> component.<br> ・For the <a href="https://docs.cluster.mu/creatorkit/en/operation-components/player-timer/">Player Timer</a> component, set <strong>Target</strong> to “Player”, <strong>Key </strong>to “Die”, and <strong>Delay Time Seconds to </strong>“1”. Press the <strong>+ button </strong>to add a Trigger item.<br> ・For the Trigger, set the <strong>Key</strong> (the text field located to the right of the “Target: Player” label) to “DeathLogic”, and <strong>Value</strong> to “Signal”.</li><li>Add another component to the GameObject, this time a <a href="https://docs.cluster.mu/creatorkit/en/operation-components/player-logic/">Player Logic</a> component.<br>・In the <a href="https://docs.cluster.mu/creatorkit/en/operation-components/player-logic/">Player Logic</a> component, set <strong>Target</strong> to “Player”, and <strong>Key</strong> to “DeathLogic”. Press the <strong>+ button</strong> twice to add two items.<br> ・Set up the two items as specified below.<br> ・“lives”, ”Integer”, “=Subtract”<br> ・ “RoomState”, “Integer”, “Player”, “lives”<br> ・ “Constant”, “Integer”, “1”<br> ・“GameOver”, “Signal”, “=LessThanOrEqual”<br> ・ “RoomState”, “Integer”, “Player”, “lives”<br> ・ “Constant”, “Integer”, “0”</li></ul><p>This does two things:</p><ul><li>When the player receives a signal named “Die”, the value of “lives” will be subtracted by 1 after a 1-second delay.</li><li>When “lives” reaches 0, the Cluster gimmick named “GameOver” will be triggered.</li></ul><h4><strong>Initializing and saving the lives count</strong></h4><p>We’ll also need to initialize the lives and save it across sessions.</p><ul><li>In the <strong>PlayerLives</strong> GameObject in the hierarchy select <strong>Add Component &gt; </strong><a href="https://docs.cluster.mu/creatorkit/en/trigger-components/initialize-player-trigger/"><strong>Initialize Player Trigger</strong></a>.<br>・Press the <strong>+ button </strong>to add an item, and set it up as specified below:<br> ・Key: “lives”<br> ・Initial Value: “Integer”<br> ・Value: “3”</li></ul><p>This will initialize the “lives” variable to 3. The value will also be retained even if the player leaves and revisits the world.</p><h3><strong>Displaying the lives count</strong></h3><p>We now have the lives count under control, but it’s not shown to the player yet. Let’s make it show up on the screen.</p><ul><li>Right-click the Hierarchy, or select the GameObject menu in the menu bar at the top. Select <strong>UI &gt; </strong><a href="https://docs.cluster.mu/creatorkit/en/world-components/player-local-ui/"><strong>PlayerLocalUI</strong></a><strong> — cluster</strong>.<br>・Note: The UI may show up very close to the camera. In that case, select it in the Hierarchy and hit the F key on the keyboard to have the camera focus on it.<br>・Right-click <strong>PlayerLocalUI/SafeArea</strong>, and select <strong>UI &gt; Legacy &gt; Text</strong> to add a Text object as its child object.<br>・Select the newly added <strong>Text (Legacy)</strong> GameObject, and in the <strong>Inspector </strong>pane, press the <strong>Add Component </strong>button, type <strong>Set Text Gimmick</strong> and add the component to the GameObject.<br>・In the <a href="https://docs.cluster.mu/creatorkit/en/gimmick-components/set-text-gimmick/">Set Text Gimmick</a>, set it up as specified below:<br> ・Target: “LocalPlayer”<br> ・Key: “lives”<br> ・Parameter Type: “Integer”<br> ・Format: “{0}”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o5wp_lk0tnq3JOeM3QgM1Q.png" /></figure><p>Try running the world, either by pressing the Play button in Unity, or by uploading the world to Cluster. The value 3, the initial lives count we set up earlier, should be visible on the screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0S_HXUeekp7_ha-D1klNnw.png" /></figure><h3><strong>Dying and decrementing the lives count</strong></h3><p>Now let’s put this to use in an actual game!<br>We’ll take the <strong>Playground (Athletic)</strong> sample in the <a href="https://medium.com/@cluster_official/recommendations-for-the-template-world-athletic-a1469f431638">Template Worlds project</a>, and modify it so the lives count will decrease when the player falls off a platform.</p><p>“Falling off a platform” can be detected by checking to see if <strong>the player avatar has entered a defined area underneath the platforms.</strong></p><ul><li>Create a new GameObject, name it “DeathArea”, and move it to an area underneath the platforms.<br>・Note: Make sure it isn’t placed lower than the Despawn Height. Also, if you have any intermediary warp targets in the level, place it higher than those.</li><li>With the DeathArea object selected, look at the Inspector pane and add a <strong>Box Collider</strong> component. Make sure the <strong>Is Trigger</strong> property is checked.<br>・The player will lose a life when entering this collider, so you should expand its dimensions to fill the area underneath all the platforms. Either modify the <strong>Size </strong>values of the Box Collider, or press the <strong>Edit Collider</strong> button and move the green boundaries of the collider.</li><li>Add an <a href="https://docs.cluster.mu/creatorkit/en/trigger-components/on-collide-item-trigger/"><strong>On Collide Item Trigger</strong></a> component.<br>・Press the <strong>+ Button</strong> to add a trigger item, and set it up as below:<br> ・Target: “CollidedItemOrPlayer”<br> ・Key (adjacent to the Target popup): “Die”<br> ・Value: “Signal”</li></ul><p>Once you’ve come this far, let’s try it out. Every time your avatar falls off a platform and enters the <strong>DeathArea</strong>, your displayed lives count should decrease.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*cbNJRVutAB5q4lo-NUWjFw.gif" /></figure><h3><strong>Warping to a different location upon Game Over</strong></h3><p>Next, let’s handle what happens when you hit Game Over.</p><p>As we’ve set things up to send a “GameOver” signal when the lives count reaches zero, we can receive that signal in a Gimmick to trigger a Game Over sequence.</p><p>In this tutorial, we’ll warp (teleport) the player to a jail cell when they hit Game Over.</p><p>Let’s start by creating the jail cell.</p><ul><li>Create an empty GameObject, and name it “Jail”. Move it to a location far away from the obstacle course, then create a jail cell by adding floors and walls as its children.<br>・You can use platform tiles from <strong>Assets/ClusterCreatorKitTemplate/Playground/Prefabs/StaticObjects</strong> for construction.</li><li>Create an empty GameObject as the child of the Jail GameObject. Name it “WarpTarget”.<br>・Move WarpTarget to the position the avatar should warp into.</li></ul><p>Now comes the part where the warp happens.</p><ul><li>Once the jail cell is done, select the “PlayerLives” object we created earlier and look at the Inspector pane.</li><li>Click the <strong>Add Component</strong> button, and add the <a href="https://docs.cluster.mu/creatorkit/en/gimmick-components/warp-player-gimmick/"><strong>Warp Player Gimmick</strong></a> component.<br>・Set up the <a href="https://docs.cluster.mu/creatorkit/en/gimmick-components/warp-player-gimmick/"><strong>Warp Player Gimmick</strong></a> component as follows:<br> ・Target: “Player”<br> ・Key: “GameOver”<br> ・Target Transform: drag &amp; drop the WarpTarget object created earlier</li></ul><p>Now, the player will warp to the jail cell when the lives count reaches zero. Confirm the behavior by trying out the world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*AR84LIeQZhkzgK1xyu2kqQ.gif" /></figure><h3><strong>Retrying on Game Over</strong></h3><p>Finally, let’s make a mechanism to let the player start over when they click a button in the jail cell.</p><p>First, we’ll set up a way to return to the starting point.</p><ul><li>Select the PlayerLives GameObject, and add a <a href="https://docs.cluster.mu/creatorkit/en/gimmick-components/respawn-player-gimmick/">Respawn Player Gimmick</a> component from the Inspector. Set it up as follows:<br>・Target: “Player”<br>・Key: “Respawn”</li><li>Now, whenever a signal named “Respawn” is sent, the player avatar will respawn from the initial starting point.<br>・Note: If you want to let the player restart from a location other than the initial starting point, use the <strong>Warp Player Gimmick</strong> instead.</li></ul><p>Now we’ll need a button to trigger this from inside the jail cell.</p><ul><li>Create an empty GameObject named “RetryButton” as a child of the “Jail” GameObject. Add an <a href="https://docs.cluster.mu/creatorkit/en/trigger-components/interact-item-trigger/">Interact Item Trigger</a> component to it.<br>・In its Inspector pane, press the + button twice to add 2 items, and set each of them up as follows:<br> ・Item 1<br> ・ Target: “Owner”<br> ・ Key: “lives”<br> ・ Value: “Integer”, “3”<br> ・Item 2<br> ・ Target: “Owner”<br> ・ Key: “Respawn”<br> ・ Value: “Signal”<br>・Right-click the RetryButton in the hierarchy and select <strong>3D Object &gt; Cube</strong> to make the button interactable.</li></ul><p>That’s it! Upload the world and test it out. Pressing the button in the jail cell should reset your lives to 3 and let you try again from the initial starting point.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*zJWGiNJaq6d7uDLrcjkTRw.gif" /></figure><p>You can carry over and use all sorts of data for continued use by combining saving features with logic components. Create richer experiences through systems that encourage repeated play!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f887bae229b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating Event-Only Objects and Staff-Only Switches]]></title>
            <link>https://medium.com/@cluster_official/creating-event-only-objects-and-staff-only-switches-63bcb944c279?source=rss-29c6ed8c5a84------2</link>
            <guid isPermaLink="false">https://medium.com/p/63bcb944c279</guid>
            <dc:creator><![CDATA[Cluster Official]]></dc:creator>
            <pubDate>Mon, 29 Jun 2026 08:23:29 GMT</pubDate>
            <atom:updated>2026-06-29T08:23:29.026Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GsfxnPoxNH6N-c2Mmr88wQ.png" /></figure><p>Starting from <a href="https://note.com/cluster_official/n/n4ed32df15e0f">Cluster Creator Kit v2.24.0</a>, new APIs have been added to let you determine whether the script was executed within a Cluster virtual <a href="https://docs.cluster.mu/creatorkit/en/event/">event</a>, and to obtain a specific player’s role (staff, guest speaker, or audience) within an event.</p><ul><li><a href="https://docs.cluster.mu/script/interfaces/ClusterScript.html#isEvent">ClusterScript.isEvent()</a></li><li><a href="https://docs.cluster.mu/script/en/classes/PlayerHandle.html#geteventrole">PlayerHandle.getEventRole()</a></li></ul><p>In this guide, we’ll show you how to use these features to create objects that only appear during events, as well as switches that can only be operated by event staff.</p><h3><strong>Objects present only during events: Using isEvent() to make Performer Colliders work only in events</strong></h3><p>In this example, we will make a specific area accessible only from staff if the world is used as an event venue, but accessible by everyone if used as a regular world. We can do this by having a <strong>Performer Collider</strong> present only during events.</p><p><em>What is a </em><strong><em>Performer Collider</em></strong><em>?</em></p><p><em>A </em><strong><em>Performer Collider</em></strong><em> is a feature that lets you set up areas accessible only to specific roles, like staff or guest speakers.</em></p><p>Normally, <strong>Performer Colliders</strong> will block passage even when the world is not used as an event venue. By following the steps below, you can make the affected areas passable for everyone during regular usage, while keeping them restricted during events.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wmpVXVPhQvyM38SokGkong.png" /></figure><h4><strong>Setup steps</strong></h4><p>First, place a <strong>Performer Collider</strong> at your desired location. Create a GameObject with a Collider, and in the Inspector, set its Layer to <strong>22: PerformerOnly</strong>.</p><p>Next, let’s create a script that hides the Performer Collider when the world is used as a regular world.</p><ul><li>In the Scene, set up the hierarchy structure of the Performer Colliders as follows:<br>・<strong>PerformerColliders </strong>[This should be an empty GameObject]<br> ・<strong>StageCollider </strong>[The GameObject created earlier. Anything with a Collider will do, eg. a Cube with its <strong>Layer </strong>set to <strong>PerformerOnly </strong>and <strong>Mesh Renderer</strong> disabled]</li><li>Select the PerformerColliders GameObject. Go to the Inspector, and add a <a href="https://docs.cluster.mu/creatorkit/en/item-components/scriptable-item/"><strong>Scriptable Item</strong></a> component via the <strong>Add Component</strong> button.<br>・Paste the following script into the <a href="https://docs.cluster.mu/creatorkit/en/item-components/scriptable-item/"><strong>Scriptable Item</strong></a>’s <strong>Source Code</strong> field:</li></ul><pre>$.onStart(() =&gt; {<br>  $.subNode(&quot;StageCollider&quot;).setEnabled($.isEvent());<br>});</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MfHZUwPaDugHgPsoCc0mBQ.png" /></figure><p>That’s it! With this setup, the space beyond the Performer Collider will be restricted to staff and guest speakers during events, but accessible to anyone when used as a regular world.</p><h3><strong>Objects restricted to staff members: Using getEventRole() to make a switch only staff can toggle</strong></h3><p>Next, let’s create a switch that only event staff members can operate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*UuiSwHjSYXDQ3Oc7uYzusw.gif" /></figure><h4><strong>Setup Steps</strong></h4><p>In this tutorial, we’ll create a switch that toggles a screen on and off.</p><ul><li>Place a Cube in your scene to act as the switch. Place the screen as its child object.<br>・The Hierarchy should look like this:<br> ・On/Off Switch<br> ・StandardMainScreen</li><li>Select the Cube we placed earlier. Go to the Inspector, and add a <a href="https://docs.cluster.mu/creatorkit/en/item-components/scriptable-item/"><strong>Scriptable Item</strong></a> component via the <strong>Add Component</strong> button.<br>・Paste the following script into the <a href="https://docs.cluster.mu/creatorkit/en/item-components/scriptable-item/"><strong>Scriptable Item</strong></a>’s <strong>Source Code</strong> field:</li></ul><pre>$.onInteract((player) =&gt; {<br>  if (player.getEventRole() === EventRole.Staff) {<br>    const mainScreen = $.subNode(&quot;StandardMainScreen&quot;);<br>    mainScreen.setEnabled(!mainScreen.getEnabled());<br>  }<br>});</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mLWQksiLZyqYrQrUuUHQzg.png" /></figure><p>Now you have created a screen toggle switch that only staff members of events can operate.</p><p>As we’ve seen, using <a href="https://docs.cluster.mu/script/en/interfaces/ClusterScript.html#isevent">ClusterScript.isEvent()</a> and <a href="https://docs.cluster.mu/script/en/classes/PlayerHandle.html#geteventrole">PlayerHandle.getEventRole()</a> makes it much easier to build event-specific features. Feel free to experiment!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63bcb944c279" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Create your own user interfaces with Player Interactive Local UI]]></title>
            <link>https://medium.com/@cluster_official/create-your-own-user-interfaces-with-player-interactive-local-ui-8858dba4c769?source=rss-29c6ed8c5a84------2</link>
            <guid isPermaLink="false">https://medium.com/p/8858dba4c769</guid>
            <dc:creator><![CDATA[Cluster Official]]></dc:creator>
            <pubDate>Thu, 28 May 2026 03:44:54 GMT</pubDate>
            <atom:updated>2026-05-28T03:44:54.163Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bbPo37fCm5N5N_KEy6lhkw.png" /></figure><p>Ever wanted to create your own custom user interface that visitors to your world can interact and use to trigger actions? With the <strong>Player Interactive Local UI</strong> feature, you can.</p><p>You can provide bespoke UIs tailored for your game worlds, or environments that simulate custom emotes.<br>This article will go through the basics of how.</p><h3><strong>Preparation</strong></h3><p>Before making use of Player Interactive Local UI, you will need to set up the CCK components in addition to the scripts.</p><h4><strong>Create a Player Local UI</strong></h4><p>First, let’s create a <a href="https://docs.cluster.mu/creatorkit/en/world-components/player-local-ui/">Player Local UI</a> to display the UI.<br>In this tutorial, we will be using a <strong>Button</strong> component.</p><ul><li>Create a <strong>PlayerLocalUI </strong>GameObject. You can do this by either right-clicking in the Hierarchy panel or clicking on the GameObject menu in the top menu bar, then selecting<strong> UI &gt; PlayerLocalUI — cluster</strong>.<br>・In the hierarchy, right-click on <strong>PlayerLocalUI/SafeArea</strong> and select <strong>UI &gt; Legacy &gt; Button</strong>.<br>・A <strong>Button </strong>GameObject will be created.<br> ・The <strong>Button </strong>should also contain a <strong>Text (Legacy)</strong> GameObject as its child. This will become the text label for the button.<br> ・If the <strong>Text (Legacy)</strong> GameObject is not there, create it by right-clicking on the <strong>Button</strong> object you just created in the hierarchy, and selecting <strong>UI &gt; Legacy &gt; Text</strong>.</li><li>Position adjustments aside, things should look like the below. At this point, the button still won’t do anything when clicked.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HKj7rAT0vsB28ExLmZofwA.png" /></figure><h4><strong>Add the Player Local UI to the Player Local Object Reference List</strong></h4><p>To reference your newly created <a href="https://docs.cluster.mu/creatorkit/en/world-components/player-local-ui/">Player Local UI</a> from scripts, you need to add it to the <a href="https://docs.cluster.mu/creatorkit/en/item-components/player-local-object-reference-list/">Player Local Object Reference List</a> component.</p><ul><li>Create a new GameObject and add the <a href="https://docs.cluster.mu/creatorkit/en/item-components/player-local-object-reference-list/">Player Local Object Reference List</a> component to it.<br>・Add a new slot to <strong>Player Local Object References</strong>.<br> ・In the <strong>Player Local Object Reference List</strong> section of the Inspector, there will be a header labeled <strong>Player Local Object References</strong>. Click the ▶︎ symbol nearby to open the references list.<br> ・On the other side of the <strong>Player Local Object References </strong>header, there will be a text field containing the number 0. Change it to 1.<br> ・Alternatively, you can also click the <strong>+</strong> button below the bottom of the references list.</li><li>Drag &amp; drop the Button GameObject we created earlier into the <strong>Target Object</strong> field of the newly created slot.<br>・The GameObject to assign to <strong>Target Object</strong> should be the one that contains the <strong>Button </strong>component.<br>・Set the <strong>Id</strong> to “screen_button” without the quotes. We will use this string to refer to it from the scripts later on.</li><li>Select the GameObject that contains the <a href="https://docs.cluster.mu/creatorkit/en/world-components/player-local-ui/">Player Local UI</a> component. Set the <strong>Sorting Order Type</strong> to <strong>Interactable</strong>.<br>・Once this is done, a button labeled “Make the selectable UI Interactable” will show up in the Inspector. Click it to make it set up the UI.<br> ・This will make your user interface interactable.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OgExIz7JVLzPE2iC3EcIdQ.png" /></figure><h4><strong>Configure the PlayerScript</strong></h4><p>Before using the sample script in this article, you will need to configure the <a href="https://docs.cluster.mu/creatorkit/en/world/cluster-script/player-script/">PlayerScript</a>.</p><ul><li>Your world must be uploaded with beta features enabled.</li><li>Right-click on the GameObject that contains the <a href="https://docs.cluster.mu/creatorkit/en/item-components/player-local-object-reference-list/">Player Local Object Reference List</a> component in the hierarchy, and select <strong>3D Object &gt; Cube</strong> to create a cube.<br>・In this sample, the Player Local UI button will initially be non-functional, but will become functional once the player interacts with this cube.</li><li>Click on the GameObject that contains the <a href="https://docs.cluster.mu/creatorkit/en/item-components/player-local-object-reference-list/">Player Local Object Reference List</a> component.<br>・Add a <a href="https://docs.cluster.mu/creatorkit/en/item-components/scriptable-item/">Scriptable Item</a> component, and assign the following script to it.</li></ul><pre>$.onInteract((player)=&gt; {<br>    $.setPlayerScript(player);<br>});</pre><ul><li>Set up the <a href="https://docs.cluster.mu/creatorkit/en/world/cluster-script/player-script/">PlayerScript</a>.<br>・Add a <a href="https://docs.cluster.mu/creatorkit/en/world/cluster-script/player-script/">Player Script</a> component to the same GameObject that you added the <a href="https://docs.cluster.mu/creatorkit/en/item-components/player-local-object-reference-list/">Player Local Object Reference List</a> and <a href="https://docs.cluster.mu/creatorkit/en/item-components/scriptable-item/">Scriptable Item</a> components earlier.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1AoiUKFt31Mf4IcZIZuvKg.png" /></figure><p>Now we’re all set with the preparations!</p><h3><strong>Sample Script</strong></h3><p>Now all we have to do is to set up the actual script of the button behaviors.<br>Here, we have a simple script that teleports the player slightly upwards when the <strong>Player Interactive Local UI </strong>button<strong> </strong>is clicked.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*x37hsmEvtsMNOaqeVlV_zg.gif" /></figure><p>In the <strong>PlayerScript </strong>component of the aforementioned GameObject, assign the following script.</p><pre>_.playerLocalObject(&quot;screen_button&quot;).getUnityComponent(&quot;Button&quot;).onClick(isDown =&gt; {<br>  if (isDown) {<br>    const pos = _.getPosition().add(new Vector3(0, 1, 0));<br>    _.setPosition(pos);<br>  }<br>});</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JJGEEv-tpqI66-MxkLieqg.png" /></figure><p>You can trigger all sorts of behaviors<strong> </strong>by calling them from within the if(isDown){} code block. Feel free to experiment!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8858dba4c769" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vibration API: Create objects that make your device vibrate!]]></title>
            <link>https://medium.com/@cluster_official/vibration-api-create-objects-that-make-your-device-vibrate-ae496a99fac7?source=rss-29c6ed8c5a84------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae496a99fac7</guid>
            <dc:creator><![CDATA[Cluster Official]]></dc:creator>
            <pubDate>Wed, 27 May 2026 07:50:56 GMT</pubDate>
            <atom:updated>2026-05-27T07:50:56.428Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3vREYhbngQ54T4zE5PFi8w.jpeg" /></figure><p>Starting from Cluster Creator Kit v2.33.0.2, the Vibration API is available for use in your worlds.</p><p>The API can be used to make your user’s device vibrate. Combined with audiovisuals, haptic feedback can enhance immersion and add more fun to your worlds. This article will go through the basics of how to incorporate vibration.</p><h3><strong>Device Configuration</strong></h3><h4><strong>Supported devices</strong></h4><ul><li>iOS/Android devices, Meta Quest, SteamVR devices</li></ul><p>The device (or its controllers) will need to support vibration in its hardware.</p><h4><strong>iOS/Android devices: Set vibration settings to On</strong></h4><p>Users on iOS/Android will need to enable vibration in the app’s settings first.</p><ul><li>Select the Cluster logo at the top right of the screen to open the menu.</li><li>Select the Gear icon to open the settings screen.</li><li>In the settings screen, select <strong>Controls.</strong></li><li>Enable <strong>Haptic Feedback &gt; Vibration </strong>to On.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*REUPrScHC6NFHe_kfPmRWw.png" /></figure><h3><strong>Creating an Object That Vibrates when Interacted</strong></h3><p>In this sample, we will be creating an item that will make the device vibrate when you interact with it.</p><ul><li>Create an object. Any object will do, such as a cube.<br>・Add a <a href="https://docs.cluster.mu/creatorkit/item-components/scriptable-item/">Scriptable Item Component</a> and a <a href="https://docs.cluster.mu/creatorkit/item-components/player-script/">Player Script Component</a> to the object, and paste the following scripts into each component.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yAvmQm-JEdDK1rzdsG1dyg.png" /></figure><h4><strong>Scriptable Item</strong></h4><pre>$.onInteract(player =&gt; {<br>  $.setPlayerScript(player);<br>  player.send(&quot;vibrate&quot;,true);<br>});</pre><h4><strong>Player Script</strong></h4><pre>const haptics = _.hapticsHandle;<br><br>_.onReceive((id, body, sender) =&gt; {<br>  if (id !== &quot;vibrate&quot;) {<br>    return;<br>  }<br>  if (!haptics.isAvailable()) {<br>    return;<br>  }<br><br>  const effect = new HapticsEffect();<br>  effect.frequency = 0.1;<br>  effect.amplitude = 1;<br>  effect.duration = 0.1;<br><br>  haptics.playEffect(effect, null);<br>});</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae496a99fac7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Audio Link: Incorporate Audio-Reactive Effects into Your World]]></title>
            <link>https://medium.com/@cluster_official/audio-link-incorporate-audio-reactive-effects-into-your-world-33d1ec948665?source=rss-29c6ed8c5a84------2</link>
            <guid isPermaLink="false">https://medium.com/p/33d1ec948665</guid>
            <dc:creator><![CDATA[Cluster Official]]></dc:creator>
            <pubDate>Wed, 22 Apr 2026 06:02:24 GMT</pubDate>
            <atom:updated>2026-04-22T06:02:24.953Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J6R-3HQDLFWUx2Ij-HR-TA.png" /></figure><p>Starting from <a href="https://note.com/cluster_official/n/n85893357dbfd">Cluster Creator Kit v2.33.0.1</a>, the <strong>Audio Link</strong> package can be used in your worlds.<br>By using shaders that support <strong>Audio Link</strong>, you can implement visual effects that react in sync with audio sources (or auxiliary audio sources) within your world. You can even modify the parameters on the fly using <strong>ClusterScript</strong>, perfect for live music performances.</p><p>Audio Link unlocks new freedoms in creating synergy between visuals and music. Definitely recommended for builders of concert venues and music-related worlds!</p><h3><strong>Installing Audio Link</strong></h3><h4><strong>Update Cluster Creator Kit to the latest version</strong></h4><p>When using Audio Link, please make sure your version of Cluster Creator Kit is up to date.<br>For update instructions, see the below documentation.<br><a href="https://docs.cluster.mu/creatorkit/en/installation/update-creatorkit/">https://docs.cluster.mu/creatorkit/en/installation/update-creatorkit/</a></p><h4><strong>Download and install the Audio Link package</strong></h4><p>The Audio Link package can be downloaded from the page below:<br><a href="https://github.com/ClusterVR/audiolink/releases/tag/2.1.0-cluster.1">https://github.com/ClusterVR/audiolink/releases/tag/2.1.0-cluster.1</a></p><p>Open the above page and download audiolink-2.1.0-cluster.1.unitypackage.<br>Once done, take the downloaded UnityPackage file and import it into your world’s Unity project.</p><p>That’s all for the installation. Next, you will need to set it up.</p><h3><strong>Setting up Audio Link</strong></h3><h4><strong>Setting up the Audio Link component</strong></h4><p>Find an <strong>Audio Source</strong> that you want <strong>Audio Link</strong> to react to.<br>It can be anything, be it background music built into the world, or an <strong>Audio Source </strong>set to output <strong>Auxiliary Audio</strong>.</p><p>Next, create an empty <strong>GameObject </strong>in the scene, and use the <strong>Inspector </strong>to add an <strong>Audio Link</strong> component to it.</p><p>In the <strong>Audio Link </strong>component, set the <strong>Audio Source</strong> to the <strong>GameObject </strong>containing the <strong>Audio Source </strong>component you want. <strong>Audio Link</strong> will now react to sounds coming in from that <strong>Audio Source</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dnvVFG_x4agVcOv6y661zg.png" /></figure><p>The Audio Link component may show a warning that reads like the below. This can be safely ignored.<br>“The current scene might be missing a main camera, this could cause issues with the AudioLink camera.”</p><p>If you can’t find the Audio Link component, make sure the Audio Link package has been installed correctly. If a version other than 2.1.0 of the package has been installed, you may encounter errors and the component may not work correctly.</p><h4><strong>Creating an audio-reactive Material</strong></h4><p>To see Audio Link in action, you will need to have <strong>Materials</strong> set up to react to changes in audio, and have those materials applied to models in the scene.</p><p>Such <strong>Materials </strong>will need to use compatible <strong>Shaders</strong>. Various special effect shaders can be found on sites like <a href="https://booth.pm/en/search/audiolink">BOOTH</a>, so try finding one that fits your needs.</p><p>Note: Some shaders may appear differently on different hardware, such as mobile devices.</p><p>A quick way to test things out is to use some of our sample shaders included in the Audio Link package.</p><p>Create a new <strong>Material</strong>. For its shader, select a shader within the <strong>AudioLink &gt; Examples</strong> subcategory. <br>Apply this material to a model within your scene.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKkUcy06euHDH5QBLbYb7Q.png" /></figure><p>Check how it works by <strong>Previewing</strong> or <strong>Uploading</strong> your world.<br>The material should change in appearance, in reaction to the sound that comes from the <strong>Audio Source</strong>. Try playing and stopping different sounds to see how the reactions change.</p><h3><strong>Modifying Parameters</strong></h3><p>You can modify Audio Link’s parameters to change its behavior, such as how strongly it reacts to sound (<strong>Gain</strong>), what frequency range it reacts to (<strong>Bass</strong>, <strong>Treble</strong>, <strong>Threshold</strong>), and how much the effects remain (<strong>Fade</strong>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aPselLr4LCizdf9gM6bu6w.png" /></figure><p>In addition to manually changing these parameters in the <strong>Inspector</strong>, you can also use <strong>ClusterScript</strong> to change these parameters programmatically.</p><p>The example below is a set of scripts that changes the parameters.</p><h3><strong>Using Scripting to change Audio Link parameters from within the world</strong></h3><p>In this example, we will place a switch in the world that causes the Audio Link parameters to change when used.<br>We will have 2 Cluster <a href="https://docs.cluster.mu/creatorkit/en/world/item/"><strong>Item</strong></a><strong> GameObjects </strong>and add scripts to each of them: one with a script to change the parameters, and another to send parameter updates to the first script.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VJthxsTHkrcfdEGxNx7b0g.png" /></figure><h4><strong>Script 1: Change the parameters</strong></h4><p>On the <strong>GameObject</strong> that contains the <strong>Audio Link</strong> component, add a <a href="https://docs.cluster.mu/creatorkit/en/item-components/scriptable-item/">Scriptable Item component</a>. The script should contain the code below.</p><p>Note: <strong>Audio Link</strong> components assigned to a non-<a href="https://docs.cluster.mu/creatorkit/en/world/item/"><strong>Item</strong></a> <strong>GameObject </strong>or a <strong>SubNode </strong>cannot be referenced. Make sure that both the <a href="https://docs.cluster.mu/creatorkit/en/item-components/scriptable-item/"><strong>Scriptable Item</strong></a> and <strong>Audio Link</strong> components are attached to the same GameObject.</p><p>Now, by sending a message with a <strong>messageType </strong>of<strong> SetAudioLinkParam </strong>to this <strong>Item</strong>, we can change each parameter of <strong>Audio Link</strong>.</p><pre>const audioLinkHandle = $.audioLink();<br><br>$.onReceive((messageType, args, sender) =&gt; {<br>    if (messageType === &quot;SetAudioLinkParams&quot;) {<br>        if (args.gain != null) {<br>            audioLinkHandle.setGain(args.gain);<br>        }<br>        if (args.bass != null) {<br>            audioLinkHandle.setBass(args.bass);<br>        }<br>        if (args.treble != null) {<br>            audioLinkHandle.setTreble(args.treble);<br>        }<br>        if (args.x0 != null) {<br>            audioLinkHandle.setCrossover0(args.x0);<br>        }<br>        if (args.x1 != null) {<br>            audioLinkHandle.setCrossover1(args.x1);<br>        }<br>        if (args.x2 != null) {<br>            audioLinkHandle.setCrossover2(args.x2);<br>        }<br>        if (args.x3 != null) {<br>            audioLinkHandle.setCrossover3(args.x3);<br>        }<br>        if (args.threshold0 != null) {<br>            audioLinkHandle.setThreshold0(args.threshold0);<br>        }<br>        if (args.threshold1 != null) {<br>            audioLinkHandle.setThreshold0(args.threshold1);<br>        }<br>        if (args.threshold2 != null) {<br>            audioLinkHandle.setThreshold0(args.threshold2);<br>        }<br>        if (args.threshold3 != null) {<br>            audioLinkHandle.setThreshold0(args.threshold3);<br>        }<br>        if (args.fadeLength != null) {<br>            audioLinkHandle.setFadeLength(args.fadeLength);<br>        }<br>        if (args.fadeExpFalloff != null) {<br>            audioLinkHandle.setFadeExpFalloff(args.fadeExpFalloff);<br>        }<br>        if (args.autogainDerate != null) {<br>            audioLinkHandle.setEnableAutogain(true);<br>            audioLinkHandle.setAutogainDerate(args.autogainDerate);<br>        }<br>        // Apply settings after all parameters have been updated<br>        audioLinkHandle.applySettings();<br>    }<br>}, { player: true, item: true });</pre><h4><strong>The Script in detail</strong></h4><pre>const audioLinkHandle = $.audioLink();</pre><p>We first obtain a handle that references the Audio Link component attached to the same Item as this script, using $.audioLink().</p><pre>audioLinkHandle.setGain(args.gain);</pre><p>We can pass values to each of Audio Link’s parameters by calling the handle’s respective setXXXX() method.<br><strong>Note that at this point, the values have not been applied to the component yet.</strong></p><pre>audioLinkHandle.applySettings();</pre><p>After setting the parameter values, call the applySettings() method to apply those changes to <strong>Audio Link</strong>.</p><h4><strong>Script 2: Send the parameter updates</strong></h4><p>Create another <strong>Item GameObject</strong>, separate from the earlier <strong>Item GameObject </strong>with the <strong>Audio Link</strong> component and the parameter change script. Add a <a href="https://docs.cluster.mu/creatorkit/en/item-components/scriptable-item/"><strong>Scriptable Item</strong></a> component and a <a href="https://docs.cluster.mu/creatorkit/en/item-components/world-item-reference-list/"><strong>World Item Reference List </strong></a>component to it. Also add a <strong>Collider </strong>so users can interact with it.</p><p>Set the <a href="https://docs.cluster.mu/creatorkit/en/item-components/scriptable-item/"><strong>Scriptable Item</strong></a> component to contain the code below. You can modify the content of audioLinkParams to your liking.</p><p>In the <a href="https://docs.cluster.mu/creatorkit/en/item-components/world-item-reference-list/"><strong>World Item Reference List </strong></a>component, set <strong>Id </strong>to “audioLink” (without the quotes), and set <strong>Item </strong>to the earlier <strong>Item GameObject</strong> containing the <strong>Audio Link</strong> component and the parameter change script.</p><pre>const audioLinkItem = $.worldItemReference(&quot;audioLink&quot;);<br>const setAudioLinkParamsMessageType = &quot;SetAudioLinkParams&quot;;<br><br>$.onInteract((player) =&gt; {<br>    // New values for Audio Link parameters<br>    // If a parameter doesn&#39;t need updating, delete that line<br>    const audioLinkParams = {<br>        gain: 1,<br>        bass: 1,<br>        treble: 1,<br>        x0: 0,<br>        x1: 0.25,<br>        x2: 0.5,<br>        x3: 0.75,<br>        threshold0: 0.45,<br>        threshold1: 0.45,<br>        threshold2: 0.45,<br>        threshold3: 0.45,<br>        fadeLength: 0.25,<br>        fadeExpFalloff: 0.75,<br>        autogainDerate: 0.1,<br>    };<br><br>    audioLinkItem.send(setAudioLinkParamsMessageType, audioLinkParams);<br>});</pre><p>Now, by moving your avatar to the <strong>Item GameObject </strong>and interacting with it, you can cause the Audio Link parameters to change.</p><p>Try experimenting with different parameter values to see how the effects change.<br>For instance:</p><pre>const audioLinkParams = {<br>    bass: 2,<br>    treble: 0.1,<br>};</pre><p>If you use the above parameters, the effects will react stronger to sounds with lower frequencies (bass).</p><p>Note: For details on each of the parameter values, see the <a href="https://docs.cluster.mu/script/en/">Script Reference</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33d1ec948665" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Control Switching Between 1st and 3rd Person Perspectives]]></title>
            <link>https://medium.com/@cluster_official/control-switching-between-1st-and-3rd-person-perspectives-59e4f1d39119?source=rss-29c6ed8c5a84------2</link>
            <guid isPermaLink="false">https://medium.com/p/59e4f1d39119</guid>
            <dc:creator><![CDATA[Cluster Official]]></dc:creator>
            <pubDate>Tue, 21 Apr 2026 04:29:28 GMT</pubDate>
            <atom:updated>2026-04-21T04:29:28.245Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BgFujM4CA1TUSirxt-pdFA.jpeg" /></figure><p>Starting from <a href="https://note.com/cluster_official/n/n31c20479713f">Cluster Creator Kit v2.37.1</a>, world creators can use scripting to programmatically control the player’s viewpoint between 1st and 3rd person perspectives.</p><p>In Cluster, players can switch between 1st and 3rd person perspectives by using the menu at the top right of the screen, or the T key on PC/Mac. Up until now, perspective switching had been solely up to the player. This feature allows world creators to force the view to switch to a given perspective, and also temporarily block the ability to manually switch.</p><p><strong>Note: </strong>This feature does not work against players in VR, who are always set to 1st person.</p><p>This can be used for many things. When a player is going up to a signboard with instructions written on them, you can switch them to 1st person for better readability. In game or horror worlds intended to be experienced in 1st person, you can ensure it gets played that way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*fHId0py88AqsGvx16rDltA.gif" /><figcaption>Example: Approaching a signboard causes the player to switch to 1st person view</figcaption></figure><h3><strong>Sample Script</strong></h3><p>Perspective switching can be done through the API calls <a href="https://docs.cluster.mu/script/interfaces/CameraHandle.html#switchtofirstpersonview"><strong>switchToFirstPersonView</strong></a>, <a href="https://docs.cluster.mu/script/interfaces/CameraHandle.html#switchtothirdpersonview"><strong>switchToThirdPersonView</strong></a>, and <a href="https://docs.cluster.mu/script/interfaces/CameraHandle.html#setperspectiveswitchinglocked"><strong>setPerspectiveSwitchingLocked</strong></a>, which all reside in the <a href="https://docs.cluster.mu/script/interfaces/CameraHandle.html"><strong>CameraHandle</strong></a> of the <a href="https://docs.cluster.mu/script/interfaces/PlayerScript.html"><strong>Player Script</strong></a><strong>.</strong>. Below is an example that locks the player camera into 3rd person perspective.</p><pre>_.onReceive((type, message, sender) =&gt; {<br>  if (type === &quot;lock&quot;) {<br>    // Lock camera into 3rd person view<br>    _.cameraHandle.setPerspectiveSwitchingLocked(true);<br>    _.cameraHandle.switchToThirdPersonView();<br>  } else if (type === &quot;unlock&quot;) {<br>    // Unlock manual perspective switching<br>    _.cameraHandle.setPerspectiveSwitchingLocked(false);<br>  }<br>});</pre><p>When this in-world gimmick activates, the player perspective will automatically switch to 3rd person, and the manual switching UI becomes disabled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*jCzlpMlhNElxkkE0S4_SjA.gif" /></figure><p>By preparing a <strong>GameObject </strong>with a <strong>Scriptable Item</strong> that sends a “lock” message to the <strong>Player Script</strong>, you can use it to lock the perspective to third-person at will. Likewise, by preparing a <strong>GameObject </strong>with a <strong>Scriptable Item</strong> that sends an “unlock” message, you can give back perspective-switching abilities to the player again..</p><p>If you aren’t familiar with scripting, you might consider having AI write the code for you. For simple in-world <strong>Gimmicks</strong>, it may be able to create functioning code. For details on AI-based coding, see the below article (Japanese).</p><p><a href="https://creator.cluster.mu/2025/07/11/ai-clusterscript">Getting AI to Write ClusterScript for You (Japanese)</a></p><h3><strong>Sample Script, in detail</strong></h3><p><a href="https://docs.cluster.mu/script/interfaces/CameraHandle.html#switchToFirstPersonView"><strong>switchToFirstPersonView</strong></a><strong> </strong>is an API that switches the view to 1st person perspective. By modifying the sample script above and replacing the mention of <a href="https://docs.cluster.mu/script/interfaces/CameraHandle.html#switchToThirdPersonView"><strong>switchToThirdPersonView</strong></a> with this, you can make the code switch the view to 1st person instead.</p><p><a href="https://docs.cluster.mu/script/interfaces/CameraHandle.html#setPerspectiveSwitchingLocked"><strong>setPerspectiveSwitchingLocked</strong></a><strong> </strong>is an API that, when set to true, prevents the player from manually switching perspectives. You can use it when you want to ensure that players experience things from a specific perspective.</p><p>As mentioned earlier, these APIs can be used to direct attention toward important instructions, or to ensure a particular perspective. For example, in a horror world, limiting the view to first-person may create a more immersive experience.</p><p>And that’s all. Try experimenting around!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59e4f1d39119" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Showing Avatar Silhouettes on Occluding Objects (3rd Person Mode)]]></title>
            <link>https://medium.com/@cluster_official/showing-avatar-silhouettes-on-occluding-objects-3rd-person-mode-0f4705e4fd99?source=rss-29c6ed8c5a84------2</link>
            <guid isPermaLink="false">https://medium.com/p/0f4705e4fd99</guid>
            <dc:creator><![CDATA[Cluster Official]]></dc:creator>
            <pubDate>Mon, 06 Apr 2026 02:58:52 GMT</pubDate>
            <atom:updated>2026-04-06T02:58:52.152Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EYMqAU28AGQ9rtQvRWMG4w.jpeg" /></figure><p>Starting from Cluster Creator Kit 2.24.0, you can make avatars show up as silhouettes when they are occluded by objects. This applies to worlds created using the Cluster Creator Kit.</p><p>Avatar silhouettes on objects can be enabled on a per-world basis. This guide will walk you through the steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IJf0ZTJ475VMh6m2yz3RWg.png" /></figure><h3><strong>Setup Overview</strong></h3><p>The outline of the steps are below. We will go into details of each individual setting in later parts of this article.</p><ul><li>In the component <a href="https://docs.cluster.mu/creatorkit/en/world-components/world-runtime-setting/"><strong>World Runtime Setting</strong></a>, set <strong>Write Own Avatar Silhouette Stencil</strong> to on</li><li>Select the objects you want silhouettes to appear on, and set their <strong>Layer</strong> to <strong>CameraOnly</strong></li><li>Create a new <strong>Material</strong> and set its <strong>Shader</strong> to our sample shader designed for silhouettes<br>・The sample shader can be found in <strong>Packages/Cluster Creator Kit/PackageResources/Shaders</strong></li><li>Select the objects you want silhouettes to appear on, and set their <strong>Material</strong> to the material you just created</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4DgC4ygMfrd8Kma08lT9fQ.png" /></figure><h4><strong>Things to be aware of</strong></h4><p>There are a few caveats to keep in mind when using silhouettes.</p><ul><li>Silhouettes only appear for your own avatar. Avatars for other users will not appear.</li><li>Silhouettes only appear for materials with ZWrite enabled.<br>・Transparent materials will not appear in silhouettes.</li><li>Silhouettes only appear while in <strong>Third Person Mode</strong>.<br>・They will not appear while in Camera Mode, VR, or First Person Mode.</li><li>Accessories and carried items will not appear in silhouettes.</li></ul><h3><strong>Setup Steps in Detail</strong></h3><h4><strong>In the World Runtime Setting component, set Write Own Avatar Silhouette Stencil to on</strong></h4><ul><li>Create a new empty GameObject, either by right-clicking the Hierarchy, or going to the GameObject menu in the menu bar and selecting <strong>Create Empty</strong>. Give it a descriptive name, such as “Settings”.<br>・Note: The location of the GameObject does not matter.</li><li>In the Inspector of the newly created GameObject, select <strong>Add Component</strong>, and add the <a href="https://docs.cluster.mu/creatorkit/en/world-components/world-runtime-setting/"><strong>World Runtime Setting</strong></a> component.<br>・Note: If the <a href="https://docs.cluster.mu/creatorkit/en/world-components/world-runtime-setting/"><strong>World Runtime Setting</strong></a> component does not show up in the component search results, make sure you have the latest version of Cluster Creator Kit installed.</li><li>In the <a href="https://docs.cluster.mu/creatorkit/en/world-components/world-runtime-setting/"><strong>World Runtime Setting</strong></a> component, set <strong>Write Own Avatar Silhouette Stencil</strong> to on. This will enable the display of avatar silhouettes on occluding objects in the world.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YuQfdxidEK3jjN42d0RDkA.png" /></figure><h4><strong>Configure the objects to show silhouettes on</strong></h4><p>Next, you will need to configure the objects you want the silhouettes to appear.</p><h4><strong>Set the Layer of the target objects to CameraOnly</strong></h4><ul><li>Select the objects you want silhouettes to appear on, and open the Inspector.<br>・Select the <strong>Layer</strong> pulldown menu, located to the lower right of the Inspector’s object name field, and select <strong>CameraOnly</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tZ0xKhjTaQVjpeYE73-SwQ.png" /></figure><h4><strong>Create a material out of the sample shader</strong></h4><p>For the silhouettes to show up on objects, they will need to be assigned materials that use a specially designed shader.<br>A sample of this shader is included with the Cluster Creator Kit, so there is no need to write a shader from scratch. For more details on shaders and materials, refer to <a href="https://medium.com/@cluster_official/learn-how-to-make-materials-to-create-cool-effects-f9ae4f2d98ef">this article.</a></p><ul><li>In the Project pane’s list of folders, select <strong>Packages/Cluster Creator Kit/PackageResources/Shaders</strong>.</li><li>Select the <strong>SilhouetteWall</strong> shader, right click on it, and select <strong>Create &gt; Material</strong> to create a new material out of it.<br>・Alternatively, you can also create a new blank material, then search for <strong>SilhouetteWall</strong> from the shader field.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C23wA_VvCulXmBcWJctgcA.png" /></figure><h4><strong>Assign the material to the target objects</strong></h4><p>Finally, you will need to assign the material you just created to the objects you want to show the silhouettes on.<br>You should not simply drag &amp; drop the material to the object — doing so will overwrite the object’s existing material. Instead, assign it as an additional material.</p><ul><li>Select the target object, and open the <strong>Inspector</strong>.</li><li>Increase the number of the material slots.<br>・Look at the <strong>__ Renderer</strong> pane. (The __ may vary. For example, the screenshot below shows “Mesh Renderer”.)<br>・The pane will have a header labeled <strong>Materials. </strong>Click the ▶︎ symbol nearby to open the materials list.<br>・On the other side of the <strong>Materials </strong>header, there will be a text field containing a number (usually 1). Increment that number by 1.<br>・Alternatively, you can also click the <strong>+</strong> button below the bottom of the materials list.</li><li>The list of materials will expand with a new <strong>Element</strong> slot. Drag &amp; drop the previously created material into the new slot. Alternatively, you can also click on the ⦿<strong> symbol</strong> to open the <strong>Select Material</strong> window, and select your material from there.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xop4UTLNJPlV0yLnNtmSKQ.png" /></figure><h3>And that’s all for the setup!</h3><p>Silhouettes give you the ability to see your location, even in tight places full of blind spots. From stealthy hide-and-seek matches to brain teaser puzzles, how you use it is up to you. We can’t wait to see what you will come up with!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0f4705e4fd99" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enabling Crouching in Worlds]]></title>
            <link>https://medium.com/@cluster_official/enabling-crouching-in-worlds-8d066927397f?source=rss-29c6ed8c5a84------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d066927397f</guid>
            <dc:creator><![CDATA[Cluster Official]]></dc:creator>
            <pubDate>Mon, 23 Mar 2026 07:39:45 GMT</pubDate>
            <atom:updated>2026-03-23T07:39:45.658Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lDTu8DarVSL-EI3GSxdpzA.png" /></figure><p>Starting from <a href="https://note.com/cluster_official/n/n9226805e7299">Cluster Creator Kit (CCK) v2.22.0</a>, you can add a setting to the <strong>World Runtime Settings</strong> to allow avatars to crouch. While crouching, avatars will be able to move through areas with low ceiling heights. This can be used to add variety to FPS-style game worlds.</p><p>This article will go through the basics of the crouching feature and steps to set it up, as well as things to keep in mind when implementing crouching.</p><h3><strong>What is Crouching?</strong></h3><h4><strong>Crouching can be done by performing an input</strong></h4><p>When inside a world with crouching enabled in the <a href="https://docs.cluster.mu/creatorkit/world-components/world-runtime-setting/">World Runtime Setting</a>, users can make their avatars crouch by performing an input, such as pressing a key.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*lklw8YBEvByLpLl97dGoJw.gif" /></figure><p>The specific inputs for crouching in Cluster’s respective supported devices are below.</p><ul><li>PC/Mac Desktop: <strong>Left Control </strong>key</li><li>Smartphone: <strong>Crouch </strong>button</li><li>PC VR &amp; Standalone VR: Physically <strong>move your head downwards</strong></li></ul><h4><strong>Crouching lets you move through low-slung spaces</strong></h4><p>Normally, avatars can move through spaces with height clearances of at least 1.3 meters (4.2 feet). When crouching, the clearance becomes 1.1 meters (3.6 feet), letting avatars move through areas with lower ceilings than usual.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*cQqesb_HrGMze1xMlNiseg.gif" /></figure><p>For more details, refer to the documentation below.</p><p><a href="https://docs.cluster.mu/creatorkit/en/world-components/world-runtime-setting/">World Runtime Setting component</a></p><h3><strong>Basic Configuration — Just Check a Box!</strong></h3><p>The basic configuration steps are below.</p><ul><li>Create a new empty GameObject, either by right-clicking the Hierarchy, or going to the GameObject menu in the menu bar and selecting <strong>Create Empty</strong>. Give it a descriptive name, such as “Settings”.<br>・In the Inspector of the newly created GameObject, select <strong>Add Component</strong>, and add the <a href="https://docs.cluster.mu/creatorkit/en/world-components/world-runtime-setting/"><strong>World Runtime Setting</strong></a> component.</li><li>In the <strong>World Runtime Setting </strong>component:<br>・Set <strong>Use Cluster HUD v2</strong> to on.<br>・Set <strong>Enable Crouch Walk</strong> to on.<br>・Note: <strong>Enable Crouch Walk</strong> will not show up until <strong>Use Cluster HUD v2</strong> is set to on.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WmWXrK1tYr9SZxpnG2dvvQ.png" /></figure><h3><strong>Notes on Using Crouching</strong></h3><h4><strong>HUD v2 introduces changes to interaction behavior</strong></h4><p>Crouching requires the Cluster HUD v2 option to be enabled.</p><p>Cluster HUD v2 is a new user interface introduced in CCK v2.18.0 which allows finer control of the UI through scripting. While it grants greater freedom of control, some knowledge of scripting may be required to make it do what you want.</p><p>HUD v2 contains some changes in behavior, such as the avatar pose when holding an item. For more details on Cluster HUD v2, refer to the documentation below.</p><p>Crouching requires the Cluster HUD v2 option to be enabled.</p><p>Cluster HUD v2 is a new user interface introduced in CCK v2.18.0 which allows finer control of the UI through scripting. While it grants greater freedom of control, some knowledge of scripting may be required to make it do what you want.</p><p>HUD v2 contains some changes in behavior, such as the avatar pose when holding an item. For more details on Cluster HUD v2, refer to the documentation below.</p><p><a href="https://docs.cluster.mu/creatorkit/en/world-components/world-runtime-setting/">World Runtime Setting component</a></p><h4><strong>Sample package available: Holding items up in HUD v2</strong></h4><p>In Cluster HUD v2, when an avatar holds an item, they will not hold them up by default. If you want to make the avatar hold items up, you will need to control the item-holding pose through scripting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*soqpiHlyYAgCCkvTcewj7g.png" /></figure><p>The Creators Guide provides a preconfigured sample package for avatar poses while holding items, compatible with Cluster HUD v2. Adapting these samples as a starting point is recommended for world creators seeking to quickly set up poses.</p><p>The sample can be downloaded from below.</p><p><a href="https://creator.cluster.mu/2024/08/16/hudv2-gun">【ベータ機能・サンプル付き】Cluster HUD v2で銃の構え方の指定・いつでもリロードできるようにしてみよう - Cluster Creators Guide｜バーチャル空間での創作を学ぶなら</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d066927397f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>