Now that BloodbornePKG updated is stable, the floodgates for modding have reopened. Here are three community-favorite mods that specifically require the new features:
Previous versions would crash when repacking chalice dungeon generation data (dungeon.pkg). The BloodbornePKG updated release fixes the block alignment bug, allowing custom chalice dungeon mods to function correctly for the first time in two years.
rally now acts as a dynamic rate limiter for I/O operations under memory pressure.
Instead of blocking on GC, bloodbornepkg.io.read() yields to the event loop with a decay‑based wait time: bloodbornepkg updated
await read(handle, buffer) # old: could hang indefinitely
await read(handle, buffer, rally=True) # new: self‑throttling
Default: rally=True for all async contexts. Set rally=False only if you control the entire memory landscape.
We’re pleased to announce the release of bloodbornepkg 1.2.0, a maintenance and feature update focused on performance, data accuracy, and expanded compatibility. Now that BloodbornePKG updated is stable, the floodgates
The previous version of BloodbornePKG could take upwards of 45 minutes to fully unpack the map.pkg and sound.pkg archives. The updated version leverages multi-threading, cutting that time down to roughly 12–15 minutes on a standard SSD.
We tested bloodbornepkg v0.7.2 vs. v1.0.0 against a mock domain with 15,000 users, 3,000 computers, and 40,000 ACL edges. Default: rally=True for all async contexts
| Metric | v0.7.2 (Legacy) | v1.0.0 (Updated) | Improvement | | ----------------------- | --------------- | ---------------- | ----------- | | Time to enum (LDAP) | 14m 22s | 8m 01s | 44% faster | | Memory peak (RSS) | 1.2 GB | 340 MB | 72% less | | JSON to JSONL conversion| N/A (monolithic)| 2.1 GB/sec write | Streaming | | Session collection | 38% timeout | 2% timeout | 95% reliability |
Note: Timed on a 2020 MacBook Pro (2.3 GHz i7) connecting to a remote DC over VPN.