Skip to content

Extend formatting rules for JBeam (minimal and complex) #123

@webdevred

Description

@webdevred

Currently, there are two configuration files for JBeam formatting:

  • minimal: compact, mostly inline formatting for nodes, flexbodies, variables, and glowMap.
    • This is the default configuration and intended as the base format.
  • complex: more detailed formatting, includes padding, decimals, and rules for slots and glowMap indicators.
    • Intended for users who want more structured formatting.

Both configurations are valid, but there are opportunities to add rules for additional JBeam sections to improve readability and consistency.

Why not everything is shipped by default

  • BeamNG has an active modding community, and we are not always certain which formatting rules users prefer.
  • To avoid enforcing unnecessary defaults, not all potential rules are shipped.
  • Community input is needed to decide which sections should have default formatting and in which configuration they belong.

Suggested areas for new rules

Vehicle components

  • Sections like axles[*], wheels[*], engine[*], and transmission[*] could maybe benefit from padding and inline formatting.

Community input needed

  • Which sections should have default formatting?
  • Which config (minimal or complex) should each rule belong to?
  • Are there preferences for inline vs. multi-line formatting for specific arrays?

Feedback is welcome to define clear defaults and expand these rules consistently, while keeping minimal as the base shipped configuration.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions