Crates.io | sl-chat-log-parser |
lib.rs | sl-chat-log-parser |
version | |
source | src |
created_at | 2025-03-07 22:19:55.832885+00 |
updated_at | 2025-03-07 23:26:36.694694+00 |
description | Parser for SL viewer chat logs (Firestorm in particular but might work for others too) |
homepage | |
repository | https://github.com/taladar/sl-map-tools |
max_upload_size | |
id | 1583744 |
Cargo.toml error: | TOML parse error at line 23, column 1 | 23 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
Parser for SL viewer chat logs (Firestorm in particular but might work for others too)
Tries to parse every possible line into something useful, the naming of the enum variants might still need some work to get into a more unified style but the hard part is done and it parses my own 15+ years of chat logs.
It is highly recommended to use release builds to parse large amounts of logs, there is a significant performance difference between debug and release builds.
Some performance optimization by reordering the parsers could probably be done but I haven't done so yet.