[adrian-andrzjewski]

Summary

• Preserve existing J3M-compatible output when getValueAsString supports the type.
• Fall back to the actual value when J3M formatting is unavailable, including readable primitive and object array contents.
• Add regression coverage for matrices, arrays, supported formatting, and null values.

Fixes #2523

Validation

• Full core test suite: gradlew.bat :jme3-core:test (passed).
• Checkstyle: gradlew.bat :jme3-core:checkstyleMain :jme3-core:checkstyleTest (both passed; existing warnings are in unrelated files).

[jaime-jmebot]

Hi, thanks for addressing this—this is a focused fix for a frustrating debugging case, and the fallback keeps MatParam.toString() useful for values that cannot be represented in J3M syntax.

I reviewed the implementation and regression tests. Preserving getValueAsString() whenever it returns a supported format avoids changing existing output, while the array-specific formatting makes unsupported array values readable instead of exposing Java’s type-and-identity strings. The tests cover matrices, primitive and object arrays, supported vector formatting, and null values, which exercises the important behavior boundaries here.

Looks good to me. Thanks for adding the regression coverage alongside the fix!

[adrian-andrzjewski]

@yaRnMcDonuts Could you review this focused fix for #2523? It preserves J3M formatting where supported and reports matrix and array values when it is not. I validated it with the full jme3-core test suite and Checkstyle.