**Changelog 1.4.0 – THE LOCAL AI Update** **Disclaimer:** The AI runs *entirely locally* and is designed to be environmentally and ethically responsible. - It does **not** harm nature or exploit any artists. - It has only **1.5 billion parameters**, making it a **very small model** by modern standards. - It consumes as much GPU energy as watching a **1440p 60fps YouTube video**. - It was **not trained on artist data**; it uses personal input and public Wikipedia datasets. - It has its own personality, and I ensured it adheres to **ethical standards**. --- ### New Features - Added **Qwen 2.5 1.5B LLM** to MateEngine! - Press **Middle Mouse Button** while hovering over the pet to open the chat window. - Runs fully locally on your GPU — no internet connection required. - Only uses GPU while processing prompts. - Note: This is a **lightweight model** and won’t handle complex tasks or coding. It’s just a small, fun feature! - Added **Resize Button** – Quickly adjust app size for 1080p, 1440p, and 4K monitors. - Added **VRM Information Panel** – Displays polygon count, VRM version, and bone status: - **Perfect** – Properly exported model. - **Failure** – Model has export issues; animations may break. - Added **Options Submenu**. - Added **Volume Sliders** – Independently control pet, effects, and menu volume. - Added **Graphics Settings**. - Added **Dance Trails** – Glowing effects on the pet’s hands during dance. Toggle on/off as desired. - Improved **Music Source Selector** – You can now whitelist or add custom audio sources for dancing. - Added **MateEngine Version Info** – View the current app version from the menu. - Menu can now be opened with **M** key or **Right-Click**. - Added full support for **VRM 1.x** and **VRM 0.x** models. - Introduced **VRM Validator Tool** in Unity Editor – Great for content creators. --- ### Improvements & Fixes - Major **Performance Optimizations**. - Fixed a **GC Error** that could appear after 6–12 hours of continuous use. - Improved **Hand Tracking** – Reduced stuttering in some animations. - Added **Discord Rich Presence** integration. - Added **Glowing Halo** for Steam users as exclusive DLC! |
||
|---|---|---|
| .. | ||
| Editor | ||
| Runtime | ||
| csc.rsp | ||
| csc.rsp.meta | ||
| DiscordRPC.xml | ||
| DiscordRPC.xml.meta | ||
| Editor.meta | ||
| LICENSE | ||
| LICENSE.meta | ||
| package.json | ||
| package.json.meta | ||
| README.md | ||
| README.md.meta | ||
| Resources.meta | ||
| Runtime.meta | ||
|
Discord RPC Unity
|
Usage
Add the package to your project and look at the sample code. For more documentation about the RPC, check the discord-rpc-csharp documentation
Check out the documentation at https://lachee.github.io/discord-rpc-unity/
Dependencies
-
At least Unity 2018, however:
- Support is only given down to Unity 2018.4.36f1 LTS
- Support is only given up to the latest LTS
-
Newtonsoft.JSON 13
- This is provided by com.unity.nuget.newtonsoft-json
- this determines the 2018.4 min spec. You can go lower, but you need to supply your own newtonsoft.json 13.0 binary.
Installation
OpenUPM 
The openupm registry is a open source package manager for Unity and provides the openupm-cli to manage your dependencies.
openupm add com.lachee.discordrpc
Manual UPM 
Use the Unity Package Manager to add a git package. Adding the git to your UPM will limit updates as Unity will not track versioning on git projects (even though they totally could with tags).
- Open the Unity Package Manager and
Add Package by git URL... https://github.com/Lachee/discord-rpc-unity.git
For local editable versions, manually clone the repo into your package folder. Note the exact spelling on destination name.
git clone https://github.com/Lachee/discord-rpc-unity.git Packages/com.lachee.discordrpc
Unity Package
Go old school and download the Unity Package and import it into your project.
- Download the
.unitypackagefrom the Releases or via the last runCreate Releaseaction. - Import that package into your Unity3D
Logging
By default, the DiscordManager will log to the Unity Console while in the Editor. To enable logging in builds, create a Development Build and a new discordrpc.log file will be generated with your app when it runs.
Licensing
The license is MIT so do what you want;
However, i do appriciate attributations where possible and a link. Also if you plan to "fix" the library and sell it, please contribute back to this project with your fixes so others can benifit too.