Looking for Help Improving a Slither.io Protocol 14 C++ Server

[bots2020]

Discussion Type

Product Feedback

Discussion Content

Hello everyone,

I'm currently working on a Slither.io private server written in C++, hosted on a VPS. The server is based on Protocol 14 and was originally developed by a friend of mine, but unfortunately he abandoned the project before it reached a stable state.

The server is functional and players can connect, move, eat food, grow, and interact with each other. However, there are still several issues that prevent it from behaving like the official Slither.io servers.

Current Problems

Some of the issues we've identified so far include:

Snake rotation does not feel smooth or accurate.
Turning speed differs from official servers.
Movement speed feels inconsistent compared to official gameplay.
Snakes sometimes appear to "shake" or "vibrate" while moving.
Position updates can look jittery under certain conditions.
Tick rate / update timing may not match the original game.
Body segments do not always follow the head smoothly.
Boosting behavior does not perfectly match official servers.
Collision detection may occasionally feel inaccurate.
Spawn behavior still needs improvement.
Network synchronization between client and server needs refinement.
Some protocol packets may not be implemented exactly as the original game.
Interpolation and prediction behavior are likely different from the official implementation.
What I'm Looking For

I'm trying to make the server behave as closely as possible to the official Slither.io experience.

If you have experience with:

Slither.io protocol reverse engineering
Game networking
Real-time multiplayer servers
C++
Entity interpolation and movement systems
Tick-based game loops

your help would be greatly appreciated.

Testing

You can compare behavior by:

Connecting to an official Slither.io server.
Using NTL Mod or another client modification for comparison.
Connecting to my private server running on VPS/Linux.
Comparing movement, rotation, speed, boosting, collisions, and overall gameplay feel.
Repository & Resources

I will provide:

The server repository.
Protocol 14 documentation.
A JavaScript implementation of the Protocol 14 client.
Access information for testing.

Unfortunately, some people who already have working private Slither.io servers have chosen not to share information or help newer developers. Because of that, I'm hoping to collaborate with the community and learn from others who are interested in the project.

Any contribution, suggestion, code review, testing, or technical advice would be greatly appreciated.

Thank you very much for your time and support! 🙂
protocol14.js

Here is the server that my friend created: https://github.com/bots2020/servidor_slither

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐