ACCServer.exe current as of writing (nightly auto-update)
Debian 12.4
Description:
After encountering difficulties with ACCWeb parsing the bop.json file from LFM, upon analysis, I once more found that ACCWeb consistently outputs bop.json files encoded in "UTF-16LE (with BOM)." However, when attempting to import the LFM bop.json, ACCWeb failed to parse the file, and ACCServer.exe ignored it after manual placement in the correct directories, even after stopping the port and ACCWeb all together.
Observations:
ACCWeb-generated bop.json files consistently use "UTF-16LE (with BOM)" encoding.
LFM BOP.json is encoded as "UTF-16LE" without BOM.
Comparison using the file command and Geany editor revealed the encoding disparity.
Enabling "Write Unicode BOM" in the editor and saving the LFM bop.json allowed successful parsing by ACCWeb.
Applying the modified LFM bop.json resulted in the correct application of positive and negative ballast during server tests.
Resolution:
The issue was resolved by manually adding the Byte Order Mark (BOM) to the LFM bop.json file using an editor that supports BOM writing, allowing ACCWeb to parse the file correctly.
Enabling BOM in Geany:
Proposal:
Consider implementing a feature in ACCWeb to dynamically check the encoding of presented bop.json files. If the encoding does not match "Unicode text, UTF-16, little-endian text, with no line terminators," automatically convert and standardize the encoding to ensure compatibility.
Benefits:
Simplifies the bop.json integration process for administrators.
Prevents parsing issues arising from inconsistent file encodings.
Enhances user satisfaction and usability of ACCWeb.
Implementation:
Integrate a mechanism within ACCWeb to identify and convert bop.json files to the specified encoding during import or server startup.
Impact:
This feature could significantly streamline bop.json management and contribute to a smoother user experience for ACCWeb administrators.
Environment:
Description: After encountering difficulties with ACCWeb parsing the bop.json file from LFM, upon analysis, I once more found that ACCWeb consistently outputs bop.json files encoded in "UTF-16LE (with BOM)." However, when attempting to import the LFM bop.json, ACCWeb failed to parse the file, and ACCServer.exe ignored it after manual placement in the correct directories, even after stopping the port and ACCWeb all together.
Observations:
filecommand and Geany editor revealed the encoding disparity.Resolution: The issue was resolved by manually adding the Byte Order Mark (BOM) to the LFM bop.json file using an editor that supports BOM writing, allowing ACCWeb to parse the file correctly.
Enabling BOM in Geany:
Proposal: Consider implementing a feature in ACCWeb to dynamically check the encoding of presented bop.json files. If the encoding does not match "Unicode text, UTF-16, little-endian text, with no line terminators," automatically convert and standardize the encoding to ensure compatibility.
Benefits:
Implementation: Integrate a mechanism within ACCWeb to identify and convert bop.json files to the specified encoding during import or server startup.
Impact: This feature could significantly streamline bop.json management and contribute to a smoother user experience for ACCWeb administrators.
Considerations: