[Enhancement] Config for hiding heightmap generation info
Closed this issue · 7 comments
Describe the bug
Server log shows up with ecliptic generate height map info, I wonder if it's possible or there's a way to hide it or not show it.
To Reproduce
Steps to reproduce the behavior:
- Install Ecliptic Season.
- Start a dedicated server.
- See log..
Expected behavior
It shouldn't flood the server log as it's not important unless it is.
Screenshots
Platform(please complete the following information):
- Minecraft Verison - 1.20.1
- Platform Verison - Forge 47.4.0
- Mod Version - EclipticSeasons-1.20.1-forge-0.11.0-pre4-7-all
Additional context
it's the base for us to check many things. and it's not a warning so you can ignore it.
i don't know why you think it's blooded. there are thousands of lines, and we only use a few tens.
You must first prove that a large amount was indeed generated—something that theoretically shouldn't happen so often, such as a complete server log.
Additionally, you should note that this mod has not yet released a stable version for 1.20+; it is still in the beta stage. For version 0.11 and above, it is in the preview beta phase. Therefore, it is important to retain this information to help investigate specific situations.
My apologies, it seems like it doesn't really spam the logs, it's something else flooding the log and I got mistaken.
There's a log if you need some information about it.
For me, I foresee in large multiplayer server, people going different direction with a straight line might still bring up the log multiple times, due to that my assumption is that each region has a heightmap generation needed for ecliptic season.
Currently I am unable to test large multiplayer server yet since its still on going development and I am trying out this mod to replace serene season.
The main idea for having a config toggle is just keeping the log clean, nothing more, nothing less. At least for a modpack developer, it's easier to see what's going on logs when it's cleaner.
Feel free to close this ticket if it's troublesome.
In fact, I’ve labeled this issue as an enhancement — though in hindsight, it might be appropriate to scale it back a bit, or be thrown into debug.log. While our development phase is coming to an end, we’re still actively collecting feedback.
The good news is that I haven’t heard of any problems related to map cache for quite a while now. You could try using a log viewer that makes it easier to filter and search through logs.
From what I’ve seen in your logs, there are about 16 relevant entries out of a total of around 75,000 messages.