> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/odk-docs/breaking-changes/v6.0.md).
# v6.0
### Configuring Player Character Input Mapping Contexts
**Date of change:** 11/12/2024
**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.*
**How to test it?**
*Ensure your input mappings are being used in PIE.*
### BPM\_ODK\_PlayerCharacterBase > Server\_TransferObjects
**Date of change:** 21/01/2025
**Affected Features:** Transfer of Data Objects to player collection
**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.*\
\&#xNAN;*When calling the `BindToDataTransferComplete` function it will return the current auth user ID and a `TransferID` that will be required for the server transfer.*\
\
**How to test it?**
*After replacing the deprecated events in your blueprints, you will receive a callback with a success or faulure message.*
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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/odk-docs/breaking-changes/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.