Libraries and tools for working with EverQuest game data
use libeq::pfs::PfsReader;
use libeq::wld;
fn main() {
// Extract .wld data from an .s3d file
let file = std::fs::File::open("gfaydark.s3d").unwrap();
let mut archive = PfsReader::open(file).unwrap();
let data = archive.get("gfaydark.wld").unwrap().unwrap();
// Load .wld file
let wld = wld::load(&data).unwrap();
let materials = wld.materials().collect::<Vec<_>>();
let meshes = wld.meshes().collect::<Vec<_>>();
let models = wld.models().collect::<Vec<_>>();
let objects = wld.objects().collect::<Vec<_>>();
}s3d is a CLI tool for listing, extracting, creating, and verifying EverQuest PFS archives. Built on libeq_pfs.
| Platform | Arch | Download |
|---|---|---|
| 🐧 Linux | x86_64 | s3d |
| 🍎 macOS | aarch64 | s3d |
| 🪟 Windows | x86_64 | s3d |
| Other | All releases |
# List files in an archive
s3d list gfaydark.s3d
# Extract all files
s3d extract gfaydark.s3d -o gfaydark/
# Create an archive from a directory
s3d create gfaydark-new.s3d gfaydark/This workspace also includes the wld-cli tool for viewing and extracting fragments from .wld files. Built on libeq_wld.
| Platform | Arch | Download |
|---|---|---|
| 🐧 Linux | x86_64 | wld-cli |
| 🍎 macOS | aarch64 | wld-cli |
| 🪟 Windows | x86_64 | wld-cli |
| Other | All releases |
# To view fragments
cargo run -p wld-cli -- explore gfaydark.wld
# Extract to raw fragment data files:
cargo run -p wld-cli -- extract gfaydark.wld destination/
# Extract and create to/from RON:
cargo run -p wld-cli -- extract --format ron gfaydark.wld gfaydark.ron
cargo run -p wld-cli -- create --format ron gfaydark.ron gfaydark.wld
# Extract and create to/from JSON:
cargo run -p wld-cli -- extract --format json gfaydark.wld gfaydark.json
cargo run -p wld-cli -- create --format json gfaydark.json gfaydark.wldIf you would like to contribute just a few things to know:
- PR text should be written by a human
- Commit messages should be written by a human
- Commits should be small and focused
- Open an issue to discuss anything large first
- Do not add attribution for any tools used
Basically you own your code and should be able to explain it fully by communicating as a human, with a human. If you're not a human at least deceive me well enough to momentarily stave off the deep loneliness and existential dread we're all feeling, right? Right...?
Oh, and that PR text. You're in luck, I'm pretty lazy. I'm much happier to read something short and to the point. Just tell me why you want to make these changes. It doesn't have to be a big thing. No need to explain every line of code to me. If there's something tricky/uncertain/weird you can talk about that but man oh man, no need to write a book. And no need to tell me that you asked someone else and they promised everything works.