Post B0dekBrzyBugxLMSzA by copygirl@fedi.anarchy.moe
 (DIR) More posts by copygirl@fedi.anarchy.moe
 (DIR) Post #B0dekBrzyBugxLMSzA by copygirl@fedi.anarchy.moe
       2025-11-26T13:23:05.997632Z
       
       0 likes, 0 repeats
       
       I’m legit stuck naming things again. Maybe fedi can help.I have an single block asset source file that gets parsed as two different assets, one for common (server+client) properties, say display name, collider, behavior, … and a client one for purely visual information like mesh, material, color, …Currently these two are called BlockType and BlockVisuals. But since they come from the same source file, should they share the same base name (BlockTypeVisuals)? I’ve also been toying with BlockDefinition and BlockAppearance.Please advice. 💚
       
 (DIR) Post #B0diIjIKVIEWKTq3oe by wolf480pl@mstdn.io
       2025-11-26T14:03:10Z
       
       0 likes, 0 repeats
       
       @copygirlBlockDefiniotion sounds good IMO.Or maybe BlockSpec?
       
 (DIR) Post #B0djBiqDtHueqmulQu by copygirl@fedi.anarchy.moe
       2025-11-26T14:12:57.895279Z
       
       0 likes, 0 repeats
       
       @wolf480pl Would it then also be BlockDefinitionVisuals, or should I just stick with what I have for that one? (It would lead to one of the types being called BlockDefinitionVisualsLoaderError.)
       
 (DIR) Post #B0dqvZsMFw902nj3jc by wolf480pl@mstdn.io
       2025-11-26T15:39:50Z
       
       0 likes, 0 repeats
       
       @copygirlOr BlockVisualsDefiniton.But it doesn't really have to be, unless you plan to have another type for representing visuals at runtme.
       
 (DIR) Post #B0dr1rQVunbQDNhKTo by wolf480pl@mstdn.io
       2025-11-26T15:40:58Z
       
       0 likes, 0 repeats
       
       @copygirloh, did you mean a common supertype, or did you mean just a common name prefix?
       
 (DIR) Post #B0dr9pS192KcP6CVPM by copygirl@fedi.anarchy.moe
       2025-11-26T15:42:14.843113Z
       
       0 likes, 0 repeats
       
       @wolf480pl No they don’t share a super type, they just both come from the same file (for now). But yeah I went for BlockDefinition and BlockVisuals for now.
       
 (DIR) Post #B0drE1pP4JWdwv8qxM by wolf480pl@mstdn.io
       2025-11-26T15:43:09Z
       
       1 likes, 0 repeats
       
       @copygirlok reading your original post again, it looks like you meant common name prefix and I misread the because I'm too Java-brained.In that case I'd go for sth like BlockSpecVisuals and BlockSpecBehaviour
       
 (DIR) Post #B0ebIRGh1KIDtswnDc by Miaourt@raru.re
       2025-11-26T22:43:31Z
       
       1 likes, 0 repeats
       
       @copygirl I'd personally go Block and BlockRender, since I guess a BlockRender can't really make sense without a parent Block anyway it might be ok to have a loose common prefix...?
       
 (DIR) Post #B0ebMDlHBDnNAV3WNM by copygirl@fedi.anarchy.moe
       2025-11-27T00:20:00.155065Z
       
       0 likes, 0 repeats
       
       @Miaourt Block is already the component added to block entities. They’ll go away when I add proper chunk meshing, but even then, I don’t think that’s a good fit.
       
 (DIR) Post #B1AZauuTZNqSC8xMMi by copygirl@fedi.anarchy.moe
       2025-12-12T10:30:55.048608Z
       
       0 likes, 0 repeats
       
       @Ginga dork :p