generated from tipragot/rust
Implement generic online system #82
Labels
No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Fix
Kind/Security
Kind/Testing
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: fish-cannard/border-wars#82
Loading…
Reference in a new issue
No description provided.
Delete branch "impl-online"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
note that the feature of adding a system to check if players are still connected will be in a new pull request.
WIP: Implement generic online systemto Implement generic online system@ -0,0 +40,4 @@
connection: Res<Connection>,
state: Res<State<CurrentScene>>,
) {
// Check if the player is an admin
Pas compris pk il doit être admin ni qui est le joueur en question
@ -0,0 +26,4 @@
/// The player is a spectator. He does not play the game.
Spectator,
/// The player is an admin. He can remove players.
Es ce que l'admin peut aussi jouer ?
The client does not check if the requests come from the server
I am dumb
I think you shoud use entities to store players to better use bevy features. And also you should separate functionnalities instead of putting everything in the same function (handle_change_player)
New commits pushed, approval review dismissed automatically according to repository settings