kawari/src/world/mod.rs

pub mod ipc;

mod zone;
pub use zone::Zone;

mod chat_handler;
pub use chat_handler::ChatHandler;

mod connection;
pub use connection::ZoneConnection;
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;`
Detect when players enter exit zones, and transistion them to the correct place It's a hack and only really works going from New -> Old Gridania, but this does work! It also means Kawari now actually requires a valid game installation, since it has to read layer group information. 2025-03-15 19:34:29 -04:00
			`mod zone;`
			`pub use zone::Zone;`
Create dedicated Connection implementations to handle future server work The current situation of throw-every-piece-of-logic-into-one-file for each server isn't working out. So now there is a new ZoneConnection/LobbyConnection struct that will be delegating tasks to their own Handlers (for example, there could be a ChatHandler.) I'm not sure how well this architecture will scale, but it's better than what we have right now. 2025-03-15 20:36:39 -04:00
			`mod chat_handler;`
			`pub use chat_handler::ChatHandler;`

			`mod connection;`
			`pub use connection::ZoneConnection;`