Find your symptom and follow the fix. If that does not help, check the records as described in “Viewing logs” below.
| Symptom | Cause | Fix |
|---|
| Setup does not finish, or an error says files cannot be replaced | The editor is running. | Close the editor and run the installer again. |
| Only the sign-in screen appears on launch | This is one of the limited public builds that require sign-in. | Sign in with your invited account. If you have no account or forgot your password, contact the person who invited you. |
| “Sign-in check failed” | The server cannot be reached. | Check your internet connection. If you have signed in once, the editor opens without internet for up to 7 days. |
| The editor locks while in use | The account was blocked during the account check that runs every 6 hours. | The editor autosaves before locking. Contact the person who invited you. |
| The AI connection (MCP) server exits immediately | In a build that requires sign-in, there is no editor sign-in info. | Sign in to the editor first. See AI connection (MCP). |
| Symptom | Cause | Fix |
|---|
| “Minecraft client jar not found” | The launcher folders do not contain that version’s jar. | Run that version once in the launcher. Then click File › Rescan launcher folder (version list). Or pick the jar yourself with File › Load jar…. |
| Blocks appear as colored boxes without textures | The jar could not be read, or that block is not in the current jar. | Apply the jar fix above first. Check the “N block types not in this jar” list in the status notification. |
| After switching to another version’s jar, some blocks look broken | They are new blocks that do not exist in that version, or blocks that were renamed. | Since 0.9.10, blocks that were only renamed (sign ↔ oak_sign · grass_path ↔ dirt_path · grass ↔ short_grass · chain ↔ iron_chain) are drawn using that jar’s name. Blocks that do not exist in that version are shown with art from a newer jar on this PC, with a notification. If there is no newer jar, they appear as colored boxes. Those blocks do not exist in the target version’s game, so replace them. |
| “No block list (server report)” | There is no cached block list for that version. | Choose a server jar with File › Build block list from server jar… (target version). Do it once per version; it takes tens of seconds. |
| “java not found” | There is no Java to build the block list. | Install Java and set JAVA_HOME or add it to PATH. Any Java that runs a server will do. |
| A newly installed version is missing from the target version list | Versions are scanned only once at startup. | Click File › Rescan launcher folder (version list). Mod loader folders (Forge, Fabric, etc.) are not listed. |
For details, see Minecraft versions.
| Symptom | Cause | Fix |
|---|
| No shortcuts work at all | The cursor is in a text field such as the Console or a search field. | Click the viewport once. Some keys, such as Ctrl+S, work even in text fields (see Shortcuts). |
| A shortcut does not work and a “has moved to another key” notification appears | That command’s key was changed in the Shortcuts window. | Check the current key in Tools › Shortcuts… or click Default. |
| World editing keys do not work | The Paint tab is showing. | Return to the World tab with Ctrl+Tab. |
| Editing keys do not work during Play | Editing shortcuts are blocked during Play. | End Play with Esc. |
| The W · E · R gizmo does not appear | Nothing is selected. | Select the Selection tool with Q, select a region, prop or actor, then press the key. |
| Other edits and saving are blocked during a long task | Tasks over 200,000 cells are applied across several frames. Other edits and saving are blocked while it runs. | Wait until the status bar progress finishes, or cancel with Esc or the status bar cancel button. Canceling also undoes the part already applied. |
| Placing while pointing at the sky creates a block in front of the camera | Where there are no blocks, the block goes on the floor (y = 0); if the floor is not visible either, it goes in midair 6 blocks in front of the camera. | Point at the ground or a block face before placing. |
| The drag box height does not go down | This is the behavior in 0.9.9 and earlier. | Update to 0.9.10 or later. |
| Undo stops working | Undo history holds up to 200 steps. Edit › Clear history empties the history. | Check the remaining steps in the Window › History panel. Keep important moments with a quick snapshot (Ctrl+Alt+S). |
| Clicking under a ceiling or floating slab plants trees on top of it | This is the behavior in 0.9.10 and earlier. | Since 0.9.11, trees are planted on the layer you clicked (the floor under the ceiling). |
| Symptom | Cause | Fix |
|---|
| Imported OBJ, FBX or glTF models are missing from the resource pack | They were imported as original shape (triangles) and cannot become Minecraft models. | In the Content Browser, right-click the model › Change import mode… and choose Display or Convert to blocks. Since 0.9.9, they are automatically converted to Display when the resource pack is built, with a warning. |
| OBJ, FBX or glTF cannot be edited in the UV Editor | UV editing works only for .bbmodel, .npmodel and custom blocks. | Import models whose UVs you want to edit as .bbmodel. |
For details, see Importing custom models · Resource pack and HUD.
| Symptom | Cause | Fix |
|---|
| Slow or stuttering on large maps | View distance and shadow distance are too large for the PC. | Click the Low-end PC preset in Tools › Performance settings…. Check FPS and the meshing queue with the Ctrl+F7 performance display. |
| The distance looks empty for a while after opening | Chunk meshes are being built. | Wait until the Meshing count in the status bar reaches 0. Increasing meshing threads makes it faster. |
| F6 Game view looks like the older approximate view | The Forward+ renderer is not available in this environment. | Update your graphics driver. |
| F7 Path tracing does not work | Compute shaders are not available in this environment. | Update your graphics driver. |
| Viewing the whole map from far away in F6, the terrain fades to sky blue | This is the game’s edge fog at the end of the render distance. | In the Atmosphere · lighting panel on the viewport bar, under Game view (F6), increase Render distance (chunks) or turn on Overview mode (editor only) (since 0.9.1, on by default). |
| The grid is not visible in F6 | Game view hides the grid. | Press G. |
| Floating windows going outside the editor is inconvenient | Since 0.9.9 they open as operating system windows. | Turn off Preferences › Appearance › Floating windows outside the editor. |
| The panel layout is messed up | — | Click Window › Reset layout. |
| You changed the language but nothing changed | The language changes only after a restart. | Restart the editor. |
| Symptom | Cause | Fix |
|---|
| You quit without saving | — | Restart and click File › Load autosave. After it opens, save it with Save As. |
| The PC shut down during a save | — | Open that world again. It is recovered from the leftover .tmp or .bak, and the notification shows “recovered”. |
| “Couldn’t read the registry; starting with an empty one” | assets\registry.json in the project folder could not be read. | Check that the file was not deleted or changed by another program. |
| A world saved as a Minecraft world is missing from the singleplayer list | It was not placed in the saves folder. | Copy the generated <name>_world folder to %APPDATA%\.minecraft\saves\ (or the saves folder of the launcher you use). |
| Zone triggers do not run in a singleplayer world | World logic is run by the server plugin NP Scene. | Build the server files in the Export window (Ctrl+Shift+E). See Export and import. |
| Symptom | Cause | Fix |
|---|
| A plugin is disabled and shows an error | When a plugin throws an exception, only that plugin is disabled and the editor keeps running (isolation). | Check the error in Tools › Plugin Manager… and reload it. Warnings are collected in Help › Plugin list. |
| A plugin is not in the list | It is not in the plugin folder. | Put it in the folder opened with Tools › Open plugin folder (%APPDATA%\NPEditor\plugins\). |
For problems on the plugin author’s side, see the plugin development Overview and the SDK troubleshooting page.
| Where | Contents |
|---|
| Output Log panel | Every notification and error written by the editor and plugins. It is the Output Log tab in the bottom area. |
| Log files | Run record files are kept in %APPDATA%\NPEditor\logs\. |
| Help › Plugin list | Loaded plugins and registration warnings |
| Help › About / Licenses | The editor version (include it when you ask for help) |