created_at2018-10-02 21:40:14.899538
updated_at2021-05-06 10:14:39.18387
descriptionA simple semi-reliable UDP protocol for multiplayer games
Justin LeFebvre (jstnlef)




Build Status Latest Version Join us on Discord MIT/Apache Lines of Code Coverage

Laminar is an application-level transport protocol which provides configurable reliability and ordering guarantees built on top of UDP. It focuses on fast-paced fps-games and provides a lightweight, message-based interface.

Laminar was designed to be used within the Amethyst game engine but is usable without it.

If you are new to laminar or networking in general, We strongly recommend taking a look at the laminar book


This library is loosely based off of Gaffer on Games and shares features similar as RakNet, Steam Socket, The idea is to provide an in rust written, low-level UDP-protocol which supports the use of cases of video games that require multiplayer features. The library itself provides a few low-level types of packets that provide different types of guarantees. The most basic are unreliable and reliable packets. Also ordering, sequencing can be done on multiple streams. For more information, read the projects, book, docs or examples.

Table of contents:


These are the features this crate provides:

  • Fragmentation
  • Unreliable packets
  • Unreliable sequenced packets
  • Reliable unordered packets
  • Reliable ordered packets
  • Reliable sequenced packets
  • Rtt estimations
  • Protocol version monitoring
  • Basic connection management
  • Heartbeat
  • Basic DoS mitigation
  • High Timing control
  • Protocol Versioning
  • Well-tested by integration and unit tests
  • Can be used by multiple threads (Sender, Receiver)


  • Handshake Protocol
  • Advanced Connection Management
  • Cryptography
  • Congestion Control

Getting Started

Add the laminar package to your Cargo.toml file.

laminar = "0.3"

Useful Links


Please check out our examples for more information.

UDP API | see more

This is an example of how to use the UDP API.

Send packets

use laminar::{Socket, Packet};

// Creates the socket
let mut socket = Socket::bind("")?;
let packet_sender = socket.get_packet_sender();
// Starts the socket, which will start a poll mechanism to receive and send messages.
let _thread = thread::spawn(move || socket.start_polling());

// Bytes to sent
let bytes = vec![...];

// Creates packets with different reliabilities
let unreliable = Packet::unreliable(destination, bytes);
let reliable = Packet::reliable_unordered(destination, bytes);

// Specifies on which stream and how to order our packets, check out our book and documentation for more information
let unreliable = Packet::unreliable_sequenced(destination, bytes, Some(1));
let reliable_sequenced = Packet::reliable_sequenced(destination, bytes, Some(2));
let reliable_ordered = Packet::reliable_ordered(destination, bytes, Some(3));

// Sends the created packets

Receive Packets

use laminar::{SocketEvent, Socket};

// Creates the socket
let mut socket = Socket::bind("")?;
let event_receiver = socket.get_event_receiver();
// Starts the socket, which will start a poll mechanism to receive and send messages.
let _thread = thread::spawn(move || socket.start_polling());

// Waits until a socket event occurs
let result = event_receiver.recv();

match result {
    Ok(socket_event) => {
        match socket_event {
            SocketEvent::Packet(packet) => {
                let endpoint: SocketAddr = packet.addr();
                let received_data: &[u8] = packet.payload();
            SocketEvent::Connect(connect_event) => { /* a client connected */ }
            SocketEvent::Timeout(timeout_event) => { /* a client timed out */ }
            SocketEvent::Disconnect(disconnect_event) => { /* a client disconnected */ }
    Err(e) => {
        println!("Something went wrong when receiving, error: {:?}", e);



This library is not fully stable yet, and there may be breaking changes to the API. For more advanced examples of using laminar, you can check out the Amethyst-Network crate.


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.


Licensed under either of

Commit count: 472

cargo fmt