Guide · Converting

YSM for Minecraft China Edition (NetEase)

Learn how to convert your Java Edition Yes Steve Model (YSM) packs into Bedrock add-ons for the Minecraft China Edition (NetEase). This guide covers the required conversion tools, Blockbench plugin setup, testing in the Developer Launcher, and fixing common animation issues.

1. Prerequisites and Restrictions

Before starting, you should already be familiar with how standard Java Edition YSM model packs are structured. Encrypted single-file models ending in .ysm cannot be read or converted—you must have the raw, unencrypted model folder.

Always respect creator rights: never convert or publish a model without explicit permission from the original author.

You will need to download two specific files and have three programs installed on your computer:

  1. ysmMain.zip: The base dependency pack used strictly for testing your converted sub-pack in the China Edition.
  2. ysm-netease-utils.js: A Blockbench plugin that automates the conversion from Java YSM to a NetEase add-on.
  3. Blockbench: The 3D modeling software used to run the conversion plugin.
  4. VSCode (Visual Studio Code): Recommended for editing JSON files and scripts when troubleshooting advanced issues.
  5. Minecraft Developer Launcher (NetEase): The official NetEase development launcher (available at https://mc.163.com/dev/), which requires a registered developer account.
Do not rename or delete ysm-netease-utils.js after installing it, or Blockbench will fail to load the plugin on future startups.

2. Installing the Blockbench Plugin

Installing the converter plugin takes only a few seconds. Drag and drop the ysm-netease-utils.js file directly into an open Blockbench window and click Confirm when prompted.

To verify that the installation succeeded, navigate to File -> Plugins in the top menu bar and check that the NetEase YSM utility appears in your list of loaded plugins.

3. Converting Your Java Model Pack

Once the plugin is active, open the YSM NetEase conversion menu inside Blockbench and follow the prompts to generate your Bedrock component pack. Both the export file path and the pack ID must use English characters only, as the China Edition does not support non-ASCII characters in paths or identifiers.

  1. Click the Select Java Edition Model Pack button and choose the unencrypted folder of the Java YSM model you want to convert.
  2. Click the Select Export Path button and pick a destination folder whose full file path contains only English letters (such as a folder on your Desktop).
  3. Enter the Author Name and Model Name. The plugin combines these two fields to generate your add-on's unique ID.
  4. Use only lowercase English letters and underscores (_) for the Author and Model names—never use spaces or special characters. Make the names descriptive enough to avoid ID conflicts with other packs.
If your Windows username contains non-English characters, exporting to the Desktop will include those characters in the path. Instead, export directly to a root folder like C:\ysm_export.

4. Testing in the NetEase Developer Launcher

With your model converted, you can test it alongside the base pack in the Minecraft Developer Launcher. You must load both the ysmMain.zip base pack and your converted sub-pack together for the model to function in-game.

  1. Open the Minecraft Developer Launcher, log in, and go to Creation -> Local Import -> Import Bedrock Component.
  2. Select ysmMain.zip, give it any project name you like, and click Import.
  3. Repeat the Local Import process to import the folder generated by the Blockbench converter plugin.
  4. Select either the main pack or your sub-pack in your project list and click the Development Test button.
  5. Choose an engine version (such as 3.1 or 3.2) to proceed to the test configuration screen.
  6. Check the boxes to enable both the main pack (ysmMain) and your converted sub-pack, and set the game mode to Creative so hostile mobs do not interrupt your testing.
  7. Click Start to launch the game and switch to your model using the standard YSM interface. If you run into bugs, you can export the diagnostic log file directly from the testing console.

5. Troubleshooting: Console Errors and First-Person Arms

Another common issue is extra or missing geometry on the first-person arm. The converter automatically builds the first-person arm from all child bones inside the RightArm group. If your model lacks a RightArm bone or nests unrelated parts under it, the first-person view will look broken.

To fix this, open your converted add-on folder in VSCode, locate the entity / geometry definition file that controls bone visibility, and find the part_visibility field. Remove any extra bone groups that should not appear in first-person, or manually add missing arm groups to the list.

friendly name 'material.tohru' not found in entity friendly name list (material.default) - check your spelling?
Error: can't find animation xxx

6. Troubleshooting: GUI, Paperdoll, and Wheel Animations

Because Bedrock Edition handles UI rendering differently from Java Edition, GUI screens only play a single dedicated animation and never run parallel animations. Keep GUI animations lightweight and free of complex logic to prevent lag and errors.

  1. Hidden parts showing in menus: The UI screens play an animation named paperpoll (or paperdoll). If parts that should be hidden are visible in the menu, open your model from resource_pack\models\entity and load resource_pack\animations\main.animation.json in Blockbench, then manually edit the paperpoll animation to scale those unwanted bones to 0.
  2. Console spam when opening the model switcher GUI: If the console floods with Error: unhandled request for unknown variable 'variable.xxx', check your gui and paperdoll animations. GUI and paperdoll views do not support Molang variables, so remove any Molang expressions from those two animations.
  3. Bones failing to appear in wheel animations: Sometimes a bone group hidden in pre_parallel (scaled to 0) refuses to show up when scaled back to 1 in a wheel animation. To fix this bug, locate the keyframes for that bone in both pre_parallel and the wheel animation, and change their interpolation mode from Linear to a matching Smooth keyframe format in both places.
Error: unhandled request for unknown variable 'variable.xxx'
Always inspect resource_pack\animations\main.animation.json first when fixing display bugs, as it holds the core animations generated during conversion.

Questions

Can I convert a downloaded .ysm file to the NetEase China Edition?

No. Single-file models ending in .ysm are encrypted and cannot be read by the conversion plugin. You can only convert unencrypted Java Edition YSM model folders that you have permission to use.

Why does my converted pack fail to load or register its ID in the Developer Launcher?

The NetEase China Edition does not support spaces or non-ASCII characters in pack IDs or file paths. Make sure your export folder path uses only English characters, and use only lowercase English letters and underscores for the Author Name and Model Name.

Why does the console spam unknown variable errors when I open the YSM model selection GUI?

Bedrock GUI and paperdoll rendering contexts do not evaluate custom Molang variables. Open main.animation.json and remove all variable.xxx references from your gui and paperdoll (or paperpoll) animations.

How do I fix a part that stays invisible during a wheel animation after being hidden in pre_parallel?

Check the scale keyframes for that bone in both the pre_parallel animation and the wheel animation. If they are set to Linear interpolation, switch both sets of keyframes to a consistent Smooth keyframe mode.

More in Converting