Expected behavior

invalid configurations should crash gracefully and not silently generate gigabytes of logs till disk is full

Observed/Actual behavior

having multipaper run on two different servers with same ip and port in server.properties caused them to try to connect to themselves when looking for the other peer.
it then realized that this server has the same name (as it is itself) and invalidated its own connection
then it reconnected itself repeating the process
at each step generating a log entry repeated millions of times per second or as fast as the hardware supports

Steps/models to reproduce

in my case i had multipaper run on two different servers on both of which they listened to on 127.0.0.1:25566 which caused looking for peers to short-circuit

Plugin and Datapack List

None

MultiPaper version

MultiPaper-1.20.1-56 (MC: 1.20.1)

Other

currently its written nowhere that the ip and port in server.properties define were it looks for other peers. this should be made clear that the value in server.properties is not only used for the usual purpose

it should also be written that both peers must have an ip set there so they can reach each other