Closed HowardZHY closed 5 months ago
It appears that for some reason there are two spaces between the prefix and the log message now. We'll change our patterns to support that.
We now detect these logs as Velocity and the underlying issue has also been solved in Velocity
https://mclo.gs/FNjpZkt another wrong example
This is a partial log which doesn't contain the velocity startup messages we detect.
If no specific software can be detected our system falls back to the log pattern that matches the most lines.
In this case that's forge because forge and velocity use very similar log patterns and forge is in the list before velocity.
This is a partial log which doesn't contain the velocity startup messages we detect.
If no specific software can be detected our system falls back to the log pattern that matches the most lines.
In this case that's forge because forge and velocity use very similar log patterns and forge is in the list before velocity.
well I think it should detect [com.velocitypowered.proxy to decide if it's velocity
https://mclo.gs/6JMQuAi a Bungee log as Forge server log
That's also a partial log.
You should just share the full log if you expect detections to work correctly.
Do you have an example of that?