kawari/src/lobby/mod.rs

mod chara_make;
pub use chara_make::CharaMake;

mod client_select_data;
pub use client_select_data::ClientSelectData;

mod connection;
pub use connection::{LobbyConnection, send_custom_world_packet};

/// The IPC packets for the Lobby connection.
pub mod ipc;
Move CharaMake up to it's super module 2025-03-17 17:19:28 -04:00			`mod chara_make;`
			`pub use chara_make::CharaMake;`

Move more structs out of the root src/ folder and into their respective server 2025-03-16 15:39:44 -04:00			`mod client_select_data;`
Show the actual character list on the lobby screen This doesn't do any actual account checking yet, but it works pretty well. 2025-03-21 21:26:32 -04:00			`pub use client_select_data::ClientSelectData;`
Document the various LobbyConnection functions, move it up to it's super module 2025-03-17 17:17:19 -04:00
			`mod connection;`
Show the actual character list on the lobby screen This doesn't do any actual account checking yet, but it works pretty well. 2025-03-21 21:26:32 -04:00			`pub use connection::{LobbyConnection, send_custom_world_packet};`
Document the various LobbyConnection functions, move it up to it's super module 2025-03-17 17:17:19 -04:00
Move CharaMake up to it's super module 2025-03-17 17:19:28 -04:00			`/// The IPC packets for the Lobby connection.`
Re-organize the IPC structures so they live in their own server-specific module My old setup of throwing all of the IPC types and opcodes into one enum was becoming unbearable. Now that we have multiple things using the same opcodes (because they can overlap) I think it's time to repay this technical debt. This overhauls the structure of the project to move IPC structs into their own modules, and separate the opcode data/lists into separate ones depending on if it's clientbound and serverbound. Nothing has changed functionall, but this is going to make it way easier to add more IPC in the future. 2025-03-16 17:43:29 -04:00			`pub mod ipc;`