max-mapper / max-mapper/voxel-server
prevent cheating
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 76
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
I realized that the current implementation as of today is an attempt to do server side physics / client side predictions in such a way that any invalid inputs (e.g. cheating) on the client side would be immediately corrected by the server
It dawned on me that this approach is really hard and that for the v1 of voxel-server it should trust the client more which has the tradeoff of allowing cheating but on the other hand drastically simplifies the amount of code/banging your head against the wall needed to get a fun multiplayer server experience going.
Cheating isn't actually a big concern of mine now that I think about it -- in minecraft you don't really attack other players, the emphasis is on editing voxels in the world.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the current server-side physics and client-prediction implementation, then determine which validation should be removed or simplified for a v1 that trusts client input. Done should mean the multiplayer experience works with the agreed tradeoff that client cheating is allowed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, game-dev
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100