Jakky89

Maybe just decrease FPS of the server in the constants to 25. I have tested it and it seems to run with lesser laggs than with 50 FPS. It's just...

It's only useful for console I think where you can't see players heads on the map... But commands can't be executed in the console as far as I know.

Yes but there is another problem: some players can have the same name and when you would show or search by id it's not easy to remember who has which...

That would be ugly for players to get kicked only because they have the same name like someone else on the server. Not really nice... So better solution: change the...

Okay implemented in my fork (also with using SQLite) with /register password (gives you an ID and stores the password in the database as blob sha224 hashed and salted). Then...

You could try to decrease FPS in the constants.py from 50 to e.g. 25. Had no issues so far.

I begun adding performance improving features like a change flagging system so that e.g. only changed entities have to be sent to clients that are near it. Also I decreased...

I don't think that it changed much because there have other optimizations be done first. Also is_bit_set before every read_x block isn't the best thing to improve performance.

Okay then it has brought something but the things that are implemented yet are very basic. We have to think more about when also e.g. mob movements/attacks, distances, damage values,...

Yes it will be implemented in future I hope. But it's difficult because most things of the Cube World protocol are unknown. The things that are implemented have been found...