Platforms:
Ubuntu Server 2X.04 LTS
CasaOS v0.4.15
Crafty Controller v4.10.X
Windows 11 Pro 25H2
Version: 26.X, 26.1X, 26.2X
Description: Recently, I found out that the server doesn’t make a logs file even though its enabled in the server properties.
Steps to Reproduce:
Download and Extract the MCBDS Server File
Enable log file/console output (“content-log-file-enabled=true” “content-log-console-output-enabled=true”)
Start/Stop the server
Go to the server files
You can see that the server log folder/file never shown
Expected Result: The server should make the logs folder/file when starting or stopping the server. I also expected that there’s a multiple log files inside it when your taking actions.
Video: https://drive.google.com/file/d/1cOn7V2mnhQq_wAlcNHjY4h2DUdT1kTOe/view?usp=drive_link
Attachments
Comments 3
You are misunderstanding what content log errors are. They are not the same as the standard logs shown in the console; content log errors only occur when there is an issue with a resource pack or behavior pack.
Since no content log errors are appearing in your console, there is no reason to expect a separate content log file to be generated. Regular logs are stored at %AppData%/Roaming/internalStorage/Dedicated_Server.txt.
Content log errors are also written to this file. However, there is still a bug: a separate file is not created even when a content log error does occur.
Thank you for helping us improve Minecraft! We saved your files: