ABP’s OX Inventory Redesign replaces the web interface of an existing ox_inventory installation. The original preview on this page matches the ABP release published by AlexBanPer on Cfx.re in September 2024, which links to fkijs/Redesign-ox_inventory. Download from that creator-linked repository and record the revision you use.
What the download contains
The repository checked September 10, 2026 contains a compiled build directory, index.scss, a README and a license file. It does not supply a complete inventory server resource. You need a working ox_inventory installation first. The interface files alone do not establish a framework bridge or compatibility with every ox_inventory v2 release.
Install the build on a test server
Back up the complete working ox_inventory resource and record its version and local changes. Download the redesign and inspect its files. Following the creator’s README, replace ox_inventory/web/build with the supplied build directory. Preserve the rest of web and the resource’s server files, configuration and images. Check that build/index.html and its referenced assets are present; avoid accidentally creating build/build.
Restart the test server under your normal maintenance procedure and reconnect a client. Inspect server and F8 errors and the inventory interface before exposing it to players. The F8 command resmon displays resource usage; it does not clear the client cache. If the old interface remains, confirm the active resource path and deployed build before deleting unrelated client data.
Test behavior as well as appearance
Compare against the original interface on the same inventory version and configuration. Test opening and closing, item images, quantities, dragging and splitting stacks, item use, shops and stashes where configured, and denied actions. Verify inventory persistence after reconnect and restart. A successful resource start does not prove that every interface action still matches the installed backend.
Test your configured slot count, scrolling, tooltips and drag targets at the screen resolutions and UI scales your players use. The release thread includes reports about right-side placement and visible slot space. Treat these as reasons to check your setup, not proof that every installation has the same defect. Keep the original build ready to restore if actions or layout fail.
Customization and maintenance limits
The supplied index.scss contains styling variables, but the delivered page loads compiled CSS and JavaScript from build/assets. Editing index.scss alone does not update those deployed assets. Keep a reproducible build process for a matching source version before making substantial changes, and compare any inventory update against your customized interface.
The README explicitly says support is not provided. This review establishes the source and installation scope; it does not certify gameplay, performance or universal compatibility, and it provides no basis for promising lifetime updates. Keep the repository revision and your original working build in the maintenance record.
Creator repository and download