bevy_replicon 0.39.5

A server-authoritative replication crate for Bevy
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

use bevy::prelude::*;
use serde::{Deserialize, Serialize};

use crate::prelude::*;

/// Stores current [`RepliconTick`].
///
/// Used only on the server. Can represent your simulation step, and is made
/// available to the client in the custom deserialization, despawn, and component
/// removal functions.
///
/// The server sends replication data in [`ServerSystems::Send`] when the state is
/// [`ServerState::Running`] any time this resource changes. You can configure
/// when the tick is incremented via [`ServerPlugin::tick_schedule`].
///
/// Note that component mutations are replicated over the unreliable channel.
/// If a component mutation message is lost, the mutation will not be resent
/// until the server's replication system runs again.
///
/// See [`ServerUpdateTick`](crate::client::ServerUpdateTick) for tracking the last received
/// tick on clients.
#[derive(Resource, Deref, Default, Serialize, Deserialize, Reflect, Debug, Clone, Copy)]
pub struct ServerTick(RepliconTick);

impl ServerTick {
    /// Increments current tick by the specified `value` and takes wrapping into account.
    #[inline]
    pub fn increment_by(&mut self, value: u32) {
        self.0 += value;
    }

    /// Same as [`Self::increment_by`], but increments only by 1.
    #[inline]
    pub fn increment(&mut self) {
        self.increment_by(1)
    }
}