Skip to main content

FreeMinecraftModels Configuration

This page covers the current config.yml settings that materially affect setup, rendering, and player interaction.

File Location​

plugins/FreeMinecraftModels/config.yml

Current Verified Settings​

setupDone​

  • Default: false
  • Controls whether the first-time setup guidance is considered complete
  • Players with broad FreeMinecraftModels permissions are reminded to run /fmm initialize while this remains false
  • The setup flow toggles this value for you; you do not need to hand-edit it during normal onboarding

useDisplayEntitiesWhenPossible​

  • Default: true
  • Tells FreeMinecraftModels to prefer display-entity rendering when the server and client path support it
  • The plugin still falls back when display entities are not available
  • Bedrock clients are a special case, so do not assume this forces the same rendering path for every player

maxModelViewDistance​

  • Default: 60
  • Limits how far modeled entities are sent to viewers
  • Lower values reduce packet and client rendering load in dense model-heavy areas

maxInteractionAndAttackDistance​

  • Default: 3
  • Applies to static and dynamic modeled entities
  • Used by the runtime interaction and hit detection checks

maxInteractionAndAttackDistanceForProps​

  • Default: 6
  • Applies to prop entities
  • This is separate from the static/dynamic entity interaction distance

sendCustomModelsToBedrockClients​

  • Default: false
  • Controls whether FreeMinecraftModels attempts to send custom models to Bedrock clients
  • If disabled, Bedrock players fall back to the underlying vanilla entity where that exists
  • If you enable it, make sure your Bedrock/Geyser/Floodgate resource-pack path is actually ready for those clients

Operational Notes​

  • /fmm reload re-imports content and regenerates the output pack, so configuration changes that affect rendering behavior are easiest to validate after a reload
  • FreeMinecraftModels only generates the resource pack; it does not host it by itself
  • ResourcePackManager is still the recommended delivery path for Java clients and the safest documented path for mixed setups

When To Change These Values​

Use this config for runtime behavior tuning, not content-package management.

  • Use /fmm initialize, /fmm setup, /fmm downloadall, and /fmm updatecontent for official package lifecycle work
  • Use the imports folder for manual .bbmodel or other local content import work
  • Use config.yml when you need to adjust render mode, visibility distance, interaction distance, or Bedrock behavior

Known Caveats​

  • The local repo has version metadata drift between plugin.yml and pom.xml, so this page intentionally documents behavior rather than pinning a hard public version string
  • Bedrock behavior depends on both this config and your broader Floodgate/Geyser/resource-pack setup, so keep claims conservative unless you have tested your exact stack