Sk0rs Arsenal Master

2.0.17

2.0.16

2.0.15

New
- The arsenal offers the same items in every scenario: the factions of all loaded mods are read even if the running scenario does not use them. Before, a scenario with few factions showed only a part of the items.
- Deploy screen: move the mouse over your saved loadout to see which items you would spawn without - icon, name and reason, and below an item what is stored in it. A long list runs through by itself.
- Settings page: new switch "Personal supply budget". It switches the game's personal supply budget on or off for the server. Off: no check when saving a loadout and none on spawn.
- Database page: a progress bar while the item list is loaded or a big save is sent.
- Database page: the Price column shows the base price of every item. Orange = set by you, normal colour = the item's own price, grey = average of comparable items.
- The price multiplier can be 0: everything is free then.

Changed
- Saved loadouts are also checked for rank on spawn (rank-locked scenarios).
- A saved loadout costs supplies by the prices of the Database page, and follows every price change by itself. Items the player loses on spawn, and what is stored in them, cost nothing.
- The personal supply budget counts in the prices of the Database page too.
- The Factions list moved from the Settings page to the Profiles page: every faction, those of the running scenario in green, with the number of items assigned to it.
- Settings page: every setting has a short description.

Fixed
- With many items, saving on the Database page could cut the player off from the server - nothing loaded any more until he joined again.
- Opening the Database page and switching to another page right away made the pages load very slowly or not at all.

2.0.14

2.0.13

2.0.12

2.0.11

2.0.10

2.0.9

2.0.8

2.0.7

2.0.6

2.0.5

2.0.4

2.0.3

2.0.2

2.0.1

- Fixed: on servers with many mods the game could fail to start with "Can't compile "Game" script module" / "Too many instructions per function". Use it together with Sk0rs Server Bible 1.1.1.

2.0.0

- Everything moved into the Server Bible: Settings - Arsenal Master with the pages Database, Categories, Profiles and Settings. The #arsenal and #arsenalaudit chat commands and the password are removed.
- Database: new table with search, filters, sorting, multi-selection and a Save button.
- Items can belong to several factions.
- New: required rank and base price per item.
- New price calculation: set price, else the item's own price, else the average of comparable items; one multiplier on top.
- Categories are managed in the game (rename, reorder, switch off, restrict, add your own). The arsenal shows them as a text list.
- Profiles now hold items, categories and settings, and can be compared with the current state.
- Mods are found by themselves; the "Mods" and "ExtraCatalogs" lists are gone.
- Items without a name are no longer taken into the arsenal.
- Saved loadouts can always be saved; items a player may not have are removed on spawn.
- The categories 1.x had built in besides the game's own no longer exist; their items show under Undefined until reassigned.
- A guide is in the Server Bible under Instructions - Arsenal Master.

1.1.3

I’m going to completely rebuild the Arsenal Master to make it more accessible for server owners. It will be built on top of my Server Bible, so that the UI stays consistent across all my current and future mods.
With this rework, I expect the Arsenal Master to become much easier to use and far more flexible to deploy.

1.1.2

Rebrand & Config Overhaul

- The mod has been renamed from PZ_Arsenal to Sk0rs Arsenal Master. No action needed on your part - your existing config, catalog database, and saved profiles are detected and migrated automatically to their new location on first load after updating. The old files are archived, not deleted.
- Added a new "Tank Ammo" category, assignable in the Datenbank editor the same way as any other manual category.
- The two previously separate config files (the main config and the extra-catalogs config) are now merged into a single Sk0r_ArsenalConfig.json. Existing installs are combined and migrated automatically.
- Config and catalog database files are now saved as properly indented, human-readable JSON instead of one long unformatted line, making manual edits and diffs much easier.
- Fixed a bug where item names or descriptions containing quotes, backslashes, or line breaks could corrupt the saved catalog file.
- New optional config setting, "AllInactive": when enabled, newly-scanned items default to Inactive instead of Active.


Stability Fix

- Fixed a crash that could occur after repeatedly opening and closing the Datenbank editor (#arsenal) before it had finished loading its item list.

1.1.1

1.1.0

1.0.36

New: Item Hover Preview
- Hovering over an item's name in the Database now shows a floating tooltip with the item's name, description, weight, and a live 3D preview image — right next to your cursor.
- The tooltip is clamped to stay within the Database window and automatically resizes to fit longer descriptions.

Improvement: Sorting Performance
- Sorting the item list by name no longer causes a brief stutter/freeze on large catalogs.

1.0.35

Fixed
- Catalog entries could endlessly duplicate on Reload: an item whose stored reference had lost its file path at some earlier point (kept as just a bare ID) was never recognized as already being in the catalog, so a fresh scan kept adding it again as "new" every single time you pressed Reload — one server accumulated over 500 duplicate copies of a single item this way. Matching now uses the stable part of the reference correctly, and a damaged entry is automatically repaired back to its full, correct form the next time it's found.
- Items with no discoverable name are no longer added to the catalog: an item that has no real display name configured at all previously showed up as a raw, meaningless identifier in the Datenbank, wasn't manageable in any useful way, and could never be cleaned up. These are now skipped during scanning, and any that already exist get removed automatically on the next Reload.

1.0.34

1.0.33

1.0.32

Fixed
- Profile Save could silently save outdated data: editing an item and immediately hitting Save (without Reloading first) could save the old catalog state instead of your changes. Save now flushes pending edits to the server first, same as Reload and Close already did.
- Datenbank could eventually stop responding after repeated open/close cycles, requiring a reconnect to fix. The Close button now correctly clears its internal state on close.

Improved
- Smoother scrolling in the Datenbank: instead of building a widget for every single catalog entry up front (hundreds on a large catalog), the row list now keeps a small pool of rows loaded around whatever you're currently looking at, filling in more above/below as you scroll. Sorting and filtering are unaffected; only very large catalogs benefit noticeably, but scrolling should feel more responsive across the board.

New
- Save now asks for confirmation (a second click within a few seconds), matching Load.
- Clicking a saved profile in the Profile Manager list now fills in the Save name field automatically, so overwriting an existing profile doesn't require retyping its name.
- Added hover highlighting to the Save/Load/Reload/Close buttons and the Datenbank's sort headers (Name/Category/Faction/Active/Verify), which previously had none.

1.0.31

1.0.30

New
- Profile Manager: The Datenbank editor's "Profile Manager" box is now functional. Save the current catalog configuration under a custom name, pick a saved profile from the list, and load it back with a confirmation step (click Load twice within a few seconds). Each saved profile shows when it was saved (server time, date and hour/minute). Profiles are stored on the server, so they're shared across everyone managing the arsenal, not tied to an individual admin's machine.

1.0.29

Fixed
- Price display on dedicated servers: The automatic pricing (introduced in the last update) was being calculated correctly on the server, but the price shown in the crate UI stayed at the item's native (often 0) value on a real dedicated server, since the client never received the computed price override over the network. Purchases were still charged correctly either way — this only affected what was displayed. The catalog sync now includes the computed price, so the crate UI shows the correct amount.