> For the complete documentation index, see [llms.txt](https://docs.humancyborgrelations.com/r2d2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.humancyborgrelations.com/r2d2/features/emotions.md). # Emotions The R2-D2 Vocalizer contains an emotional AI powered by a dataset derived from R2's on-screen emotional progression. The AI tracks a stripped down set of Paul Ekman's core emotions: * Happiness * Sadness * Anger * Fear These four emotions — and the gradients between them — encompass R2's emotional range. For example, R2 can feel sentimental by being sad and happy. He can feel sassy by being happy and angry. He can feel excited by being scared and happy. The vocalizer begins in an emotionally neutral state. When an emotional stimulus or electrocution is triggered, the AI processes the stimulus and adjusts R2's emotional state. This new emotional state is reflected in the vocal response. In the absence of stimuli, R2's emotional state will drift towards neutral at a rate dictated by the AI unless the Personality Chip Override is enabled. ### Personality Chip Override When the Personality Chip Override is enabled, R2's emotions are locked in place and will not shift over time or in response to stimuli. --- # 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, and the optional `goal` query parameter: ``` GET https://docs.humancyborgrelations.com/r2d2/features/emotions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.