search

CommonMCOBJ / CommonMCOBJ

CommonMCOBJ is a spec to allow Minecraft OBJ exporters to provide extra metadata about the source world and OBJ (that would otherwise be lost) in a standard way.
5 stars 1 forks source link

Adding the Requirement for Exporters to Export Proper Block State #5

Closed StandingPadAnimations closed 4 months ago

StandingPadAnimations commented 7 months ago

(Quoting from #4)

One area where there seems to be a discrepancy between in-game and exported OBJs is with block states. Minecraft allows editing blocks state in-game for creativity purposes. Some examples include:

  • Preventing blocks such as walls, fences, and glass panes from being chained
  • Allowing blocks to float that normally wouldn't be allowed (take levers for instance)
  • Etc.

Although CommonMCOBJ states as a non-goal

  • Governing every behavior in Minecraft OBJ exporters; that would be hard to adopt and stifle experimentation,

I think an exception can be made here as it's a vanilla game feature with legitimate use, and expands creative opportunities for artists. Granted, it may cause exports to be slower, but ultimately, exports shouldn't look different from how they look in game.

As such, I propose we add the following section to CommonMCOBJ for V2 of the spec (2025):

Block States

OBJ exporters following the CommonMCOBJ spec shall export the proper block state for all blocks. If an option to only check a pre-determined list of blocks for states exists to speed up exports, it shall not be enabled by default.

EDIT 01/04/2024: if wanted, we could change the description of CommonMCOBJ to the following in V2:

CommonMCOBJ is a spec to allow exported Minecraft OBJs to be closer their in-game counterparts, by creating a common standard for OBJs and creating extra metadata for details that would otherwise be lost.

StandingPadAnimations commented 4 months ago

Merging as no objections have been raised