Minecraft Java Edition

BBS Mod Troubleshooting

Find the cause. Get back to creating.

Work through startup errors, missing models, preview issues, and video recording problems with clear checks for your BBS Mod setup.

Find your issue Installation guide
  • Animation
  • Roleplay
  • Machinima

Start with the error details

Find the BBS Mod Error Log

A problem is easier to investigate when you know what happened just before it appeared. Keep the error message and the matching game log together before changing your setup.

  1. Write down the action that failed

    Be specific about the last thing you did. Did Minecraft stop before the main menu, or did the problem appear after opening a particular film? If an error window appears, copy its full wording or take a screenshot before closing it. Keep any named file, mod or dependency in the message.

    Useful example: “Minecraft reaches the main menu. My world opens, but opening one saved film closes the game.” This gives you a clear action to check again after making a change.

  2. Open the folder for the profile you launched

    Use the game directory assigned to your BBS Mod profile. With a third-party launcher, look for an option such as Open Instance Folder. Separate profiles can use separate directories, so the default Minecraft folder may contain a log from a different setup.

    Inside the active game directory, look for the logs folder. If a crash report was generated, it will be in crash-reports.

  3. Keep the files from the affected session

    Match the file time to the session in which the problem happened. Copy the relevant files into a separate folder before another launch, so your next test stays separate from the original error. Open text files with a text editor.

    logs/latest.log
    The current game session log. Keep this even when Minecraft stays open but something in the editor stops working. Older session logs may be stored as dated .log.gz files.
    crash-reports/
    Check for a report matching the crash time. It contains crash-specific information; it does not replace the full game log. If no matching report exists, keep the available log and the visible error message.

Change one thing per test. Note what you changed and whether the same action still fails. A single warning line is a clue to investigate; keep the surrounding log context before deciding which part of the setup needs attention.

When Minecraft will not launch

Fix BBS Mod Startup Errors

Start with the wording in the loader window or game log. A missing dependency, an unsupported Java version and a mod conflict need different fixes. Use the matching check below.

Missing or incompatible dependency

Follow the named requirement

Read which mod needs the dependency and which version it requests. If the dependency is already installed, compare its Minecraft version and loader with your active profile. A file being present does not mean it is the compatible build.

For the Connector route on Forge 1.20.1 or NeoForge 1.21.1, check the Connector setup requirements. That route has its own dependency set. Keep it separate from the native Forge 1.12.2 setup.

Java runtime error

Check the Java version the game actually uses

An UnsupportedClassVersionError saying that a class was compiled by a more recent Java runtime points to code that your current runtime is too old to run. Check both the affected mod build and the Java requirement for your Minecraft and loader combination.

Inspect the Java runtime selected in the launcher profile or instance settings. Installing another Java version does not by itself confirm that this profile uses it. If a crash report is available, its System Details section can help you check the runtime used in that session.

Duplicate mod message

Use the reported file paths to find the overlap

If the loader reports duplicate versions or a repeated mod ID, inspect the files it names. An older release may still be beside its replacement. Close Minecraft and move the extra standalone file outside the active mods folder, keeping the build that matches your setup.

Work from the reported paths, especially if the filenames look different. Do not unpack mod JARs or remove libraries from inside them. If the duplicate is supplied by another mod, check for compatible releases of the affected mods.

Mixin or mod-loading crash

Test the combination before blaming one mod

A mod name in a stack trace is a useful lead, but it does not always identify which mod is at fault. First correct any explicit version or dependency errors. Then try a separate test instance with the same Minecraft version, loader, BBS Mod build and required dependencies.

If that setup launches, add the other mods back in groups, keeping each mod with its dependencies. When the crash returns, split the last group into smaller groups and test again. Keep your existing project world out of this isolation test.

What counts as progress? Reaching the main menu clears the immediate startup failure. Next, open a new test world and check that the editor opens. A successful launch alone does not verify every model, film or recording feature.

When the editor opens but the picture looks wrong

Fix a Black, Blank or Flickering Preview

First check whether the whole preview is affected or only one actor. Then compare the same scene with shaders switched off. These checks help separate a scene setup issue from a rendering conflict.

  1. Check what is missing from the picture

    If the world is visible but an actor is missing, select that actor’s replay and check its enabled state. In BBS 2.2 and later, also check Visible range in the replay properties. Move the timeline cursor inside that range and confirm that the actor’s position is inside the camera frame.

    If the entire picture is black or distorted, continue with the shader check below. For a useful comparison, create a small test film in a test world using a built-in player form in daylight, with no custom model or extra effect clips.

    Compare the results: If the test film displays correctly but your original film does not, investigate that film’s camera, replay properties and effects before changing the entire mod setup.

  2. Compare the same shot with shaders off

    BBS 2.2 introduced a shader toggle in the film preview. Use it to turn the shader pack off, then inspect the same frame again. If your version does not have that control, disable the shader pack through your shader mod’s settings.

    Keep the film, camera position and timeline time unchanged for this comparison. If the picture returns with shaders off, that points toward the shader or its interaction with the rendering setup. It does not prove that every shader pack will fail.

  3. Check mods that match the visible symptom

    The BBS developer wiki lists these user-reported interactions. They are leads to test in your own version combination, rather than confirmed failures in every release.

    Mod to check Reported symptom
    Blur+ Film-editor preview is disrupted.
    Dynamic FPS Screen flickers when Minecraft loses window focus.
    ResolutionControl+ Mobs appear shifted in the preview after changing resolution.
    Stellarity Film-editor preview turns black.

    If one of these matches your setup, use the mod isolation check above to compare the affected configuration with a separate test instance. Keep required dependencies together during testing.

Still seeing the problem? Keep screenshots of the same frame with shaders on and off. Note whether the issue affects every film, one film or only one form, and whether it happens when the window loses focus. Save the matching game log alongside those details.

When a custom asset does not look right

Fix Custom Models and Missing Textures

Check where the problem first appears: in the model list, in the model’s shape or on its surface. Each symptom points to a different part of the export to inspect.

Model is not listed

Check the export and its destination

Open the models folder from the BBS Dashboard utilities rather than guessing which Minecraft installation contains it. Confirm that your model has its own folder there and contains a .bbs.json export made with BBS Model Ex/importer. The folder name becomes the model’s ID.

Reopen the form picker after correcting the files. If the model still does not appear, check the matching game log for an error naming that asset. For the complete export workflow, follow the custom model guide .

Parts of the model are missing

Inspect the missing pieces in Blockbench

Locate a missing cube or mesh in the Blockbench Outliner. BBS expects at least one group, and geometry must belong to top-level groups. A loose cube or mesh outside those groups can be discarded during export.

Correct the hierarchy in a copy of your source project, export again and compare the same part from the same angle. For example, check a missing sleeve on its own before adjusting the whole character. Changing the replay’s position will not repair geometry that never reached the exported model.

Shape is visible but the texture is wrong

Compare the PNG with the model’s UV layout

Confirm that the exported PNG is in the same model folder as the BBS model file. Open that PNG and compare it with the texture used by your source project. An older image can leave recent paint changes missing even when the model export is current.

If colours appear on the wrong faces, inspect the affected face in Blockbench’s UV panel. UV mapping controls which part of the image lands on that face. After correcting the mapping, export the model again and include the matching texture. Renaming an unrelated PNG will not make its layout fit.

Does the entire preview turn black? Compare a built-in form in the same scene and use the preview and shader checks. If only the custom asset fails, keep the investigation focused on that model and its texture.

When a capture does not finish as expected

Fix BBS Mod Video Recording and FFmpeg Errors

Check whether the encoder fails to start, the capture stops partway through or the finished file looks wrong. Keep the exact error text and use the matching check before recording the whole film again.

FFmpeg does not start

Test the executable selected in BBS

Find the file used by Encoder path and check that it still exists. If you moved or replaced FFmpeg, the saved path may point to its old location. Run that exact executable from a terminal or Command Prompt with -version to check whether it starts.

Testing a different FFmpeg installation will not verify the file BBS is using. If the selected executable cannot run, resolve that error first. Version information confirms that it launches; it does not confirm that every encoding setting will work. For setup instructions, use the video export guide.

Capture stops or no usable file is saved

Read the failure before changing output settings

Check the recording message and the log from that session. If an error names a file or directory, identify whether it refers to the encoder, an input asset or the output location. Permission denied and No space left on device call for different checks.

Check access to the named location or available space on the affected drive. If you changed encoding options before the failure, note those changes and test the previous working settings on a short film segment. Use a new output filename so the test does not replace a useful capture.

Recording is much slower than expected

Reduce the work for a short comparison

If the progress counter is advancing, slow capture alone does not show that the video is broken. Compare a short segment with shaders off and a lower output resolution. Keep the same segment so you can judge whether the change affects recording speed.

In BBS 2.4, Render scale can render a larger picture before reducing it to the output size, which costs rendering time. If you increased it, try 1 for this comparison. Keep a note of your final-quality settings before changing them.

A video is saved, but the result is wrong

Compare the saved file with the same moment in the film

Let the recording finish, then play the saved video outside Minecraft. For a black frame or missing actor, inspect that same timeline moment in the editor and follow the preview checks. If the problem already appears in the scene, correct it there before changing encoder settings.

For missing audio, check that the intended clip is audible at that point in the project. Note whether the capture failed during its finishing stage. BBS 2.4 fixed a Linux issue with combining audio tracks and recorded video; if that matches an older setup, check the available release for your Minecraft version on the download page.

Before another full capture: Test a short section containing the affected movement or audio. Check the saved result, then restore the quality settings you intend to use. Keep the BBS version, FFmpeg version and any error message together if the failure continues.

More troubleshooting answers

BBS Mod Troubleshooting FAQ

Check control conflicts, uneven mob animation, blurry textures and options for recovering an earlier film edit. Open a question for the checks that apply to your setup.

Why does an editor shortcut stop working after I change a keybind?

Check the binding in the editor context where you want to use it. The F9 keybind list shows currently available shortcuts, and BBS 2 allows editing bindings there. Finish typing in any text field, return to the relevant panel and test the assigned key again. Change one binding at a time so you can identify which adjustment helped.

Why do WASD actor controls or Record Current Replay fail with TaCZ installed?

The BBS developer wiki lists a reported TaCZ conflict affecting actor controls and Record Current Replay. Test your exact versions in a separate instance without TaCZ, keeping required BBS dependencies. If the controls work there, investigate that mod combination before changing the film.

Why do mob animations look uneven when the camera is far from my player?

BBS documents this behaviour with Entity Model Features and resource packs when the player is far from the mob. Move your player closer and compare the same animation. If it becomes smoother, investigate the distance-related interaction before changing recording settings.

Why are form textures blurry even though the PNG looks sharp?

Reported compatibility issues include blurry form textures with Modular Force Field System, Polytone and Rainbow’s Foliage Polytone. If installed, test without the relevant mod in a separate instance. Compare the same form and PNG before repainting it; the report does not establish a fault in every release.

Can I recover a film edit from before the problem started?

BBS 2.3 introduced View backups in the film editor. If your build includes it, check whether a backup from before the unwanted edit is available. Preserve the current film before trying an earlier copy, then inspect the result before continuing work. The presence of this control does not guarantee that a suitable backup exists for every film.

Should I delete the whole BBS configuration folder to fix an error?

Keep your existing data while you investigate. A broad folder deletion can remove more than the setting you meant to reset. First test a fresh, separate instance or change only a setting identified by the error. If you need to test a specific configuration file, close Minecraft and keep a copy before moving or editing it.