Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

General-block model spawning #77

Closed
TheDuckCow opened this issue Aug 5, 2019 · 5 comments · Fixed by #168
Closed

General-block model spawning #77

TheDuckCow opened this issue Aug 5, 2019 · 5 comments · Fixed by #168
Labels
enhancement Feature requests or new functionality suggestions
Milestone

Comments

@TheDuckCow
Copy link
Member

TheDuckCow commented Aug 5, 2019

Vision

Ability to one-click add any block, not just those custom blocks stored in the meshswap file

Approach

  • Create a reference for all major block types
  • Create a mapping of material names/block names to the block types
    • Note to self: sounds very manual and will likely get out of date very often, a risk of implementing this feature. Try where possible to future proof and infer block types.
    • Could for instance default to assume basic cube as the block model
  • Support custom block models by directly reading resource pack model definitions
    • Requires implementing of UV mapping and model creation
    • Can segue this into an alternative way of running meshswap
    • Could potentially tie this in with the Mineways exporter to include custom models directly.
  • Decide whether to complete deprecate the meshswap lib, make it connected per resource pack, or even merging it with the concept of the material sync library (so there's just one utility blend file, again set per resource pack).

Additional research links

@TheDuckCow TheDuckCow added the enhancement Feature requests or new functionality suggestions label Aug 5, 2019
@Wissotsky
Copy link

Is this being worked on, or maybe there is a way to do it manually?

@TheDuckCow
Copy link
Member Author

Sorry for the delay @SkyDiverCool, it's not there yet, but I still have plans for it.

In the meantime, you can do this manually. If you take e.g. BoxScapeStudio's rig pack (which includes a file with all blocks), you can import the models there via the normal blender import process, or even copy those models into the meshswap blend file (in the MCprep addon folder under blender settings), and by making each block a group/collection (centered on itself), you'd be able to use the spawning like you wish.

@TheDuckCow
Copy link
Member Author

Not a code update, but an encapsulation of a general +1 to this feature. An existing jmc2obj user is running into errors exporting custom resource pack models in the program directly, therefore it would be helpful to at least have MCprep directly read the models found in resource packs.

Generally this request is inline with the core request here. One side thought this generates, is potentially the ability to use MCprep to more quickly and rapidly author and test Minecraft resource packs by exporting models from Blender, as it essentially would be using the same engine (but in reverse).

TODO: Collect reference resource packs with custom models to start exploring.

@TheDuckCow
Copy link
Member Author

While the main branch is merged, some work remains to add test runners for this, do some style cleanup, and add a UI and spawner code for it. Will keep this issue open until that is done.

@TheDuckCow
Copy link
Member Author

Closing this now as the feature is now polished with a UI wrapped around! Any future bugs or improvements can be added with new issue reports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature requests or new functionality suggestions
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants