# v6.0 Summary ODK v6.0 Release : The latest version of the ODK, v6.0, delivers enhanced example content tailored for Otherside creators. #### New Features * **Editor Widget for creating duplicate ABPs** * Deflector shield matching Dragon aesthetic * ODK Empty Template **Example Content** * **Otherside Teleportation** * portal examples in Boneyard and Combat Templates * portal examples between Boneyard and Combat Templates * **\[Combat Template] Role Granting system** * award a specific role to use under specific game logic condition * eg: user becomes a Titan once he is the first on the leaderboard **Improvements** * **Unreal NFT revocation logic** * removing permissions in Unreal when NFTs are revoken mid Unreal session * **Controller Updates** * Remapping via controls screen * Cursor reticle with controller on Avatar menu * **Koda Cam Improvements** * Collection Photo Album * UI Updates * Scan feature updates * Feature general improvements and polish related to camera movement and controller * Koda AnimBp needs updating to handle KodaCam animations * Update Selfie stick visuals * **Updated legacy web browser logic to use new WebUI** #### Bug Fixes * User is able to see the avatar's hands in first person mode when it shouldn't * Perfomance drops and the applications freezes on a Boneyard deployment for GFN and Local clients * Gun inherits the grenade's cooldown and cannot be used again until the cooldown period has ended * Users in different teams can’t hurt or kill each other using the gun * \[Koda Cam]The "Y" and "N" shortcut keys do not perform any action when the user presses them on the keyboard. * \[Koda Cam] Gallery Page UI shows 1/0 when no pictures are uploaded. * Orbit mode is controller-only, with the POV starting below the avatar and inside for Meebit and Koda * Some shortcuts are not accessible via the keyboard or the controller * Faceplates broken on MAC clients * Emote Wheel cannot be opened with keybinds for Keyboard and Controller for Combat Map * \[Koda Cam] Rotating the camera also rotates the avatar's position in Combat Map * HUD shortcuts don't match in Orbit mode * \[Koda Cam] The Orbit Camera UI has a missing or corrupted icon for Keyboard devices * \[Koda Cam] Zooming out makes the camera clips through the map for the Koda Avatar * User has no way of launching a grenade with a Controller * User cannot select a team with a Controller * Gun attachment disappears when the user opens the Setting Menu while Koda Cam is active * Koda Avatars cannot enter the NFT Designated Area (Small Hutt) inside the Boneyard Map * \[Koda Cam] Controller UI instructions are incorrect for Camera Offset L/R * \[Koda Cam] Adaptive UI is flickering if there is sublte input from KB/M when the Controller is active * \[Koda Cam] Frequent switching of Selfie Stick Koda Cam on and off causes screen jitter * Emotes on different sets appear on the wheel before the page has a chance to load * NFT Picture frame should only accept Koda cam pictures /avatars, nothing else * Grenades have no collision and do not explode * Rotating the camera with RMB loses functionality after using an Emote in the Combat Map * User cannot navigate between Emote Sets using the Controller inputs * Voyager Hand is clipping when the Koda Cam/Selfie mode is used * Koda Cam images don't disappear from the in game UI without restarting the client once deleted/removed * Gucci trail doesn't respect crowd transitions * The user is unable to close the In-Game Menu using the controller #### Breaking Changes * **ODK Chapter 6** has ingested V33 of Msquared - please also review any Breaking Changes listed for these releases. {% embed url="" %} ## Breaking Changes waiting for next release (v6.0) Configuring Player Character Input Mapping Contexts Date of change: 11/12/2024 CL: Affected Features: Input What’s broken and why? The way we configure the default input mapping context on a character is changing to allow us to add IMCs to the base ODK player character. How to fix it? You should override GetDefaultInputMappingContexts in the following way. Create a new local variable in your function and configure it to have the extra input mapping contexts you need.
#### BPM\_ODK\_PlayerCharacterBase > Server\_TransferObjects Date of change: 21/01/2025 CL: Affected Features: Transfer of Data Objects to player collection Point of contact: [Matt Laverick](mailto:undefined) What’s broken and why? The event Server\_TransferObjects has been deprecated and should be replaced with Server\_TransferDataObjects. This event allows for a client side callback with a success/failure message. How to fix it? Please use the `BindToDataTransferComplete` function and the `Server_TransferDataObjects` event instead of the `Server_TransferObjects` event.\ When calling the `BindToDataTransferComplete` function it will return the current auth user ID and a `TransferID` that will be required for the server transfer.\ \ ![](/files/vkOogtnYDP9AF456Ub7K) How to test it? After replacing the deprecated events in your blueprints, you will receive a callback with a success or failure message. #### Miscellaneous * **Known Issues:** * Crashes occur on both GFN and clients when the user interacts with the teleporter * Gun attachment disappears when the user opens the Setting Menu while Koda Cam is active * Titan avatars are displayed in an jitterring and overlapped state when grinding on the rails * \[Koda Cam] The user has different animations when floating while using selfie mode * \[Koda Cam] Zooming out makes the camera clips through the map for the Koda Avatar * **Documentation Updates**: N/A *** #### How to Upgrade * Please use the ODK Dashboard for any Chapter Updates. ODK Launcher will update automatically. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.otherside.xyz/release-notes/releases/v6.0.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.