Eleven Resources With Little in Common
Eleven listings that share a page rather than a theme. Read each one on its own terms here: there is no common framework requirement and no dependency chain across them, because they were never built as a set.
What is actually on this page
Four rough groups, and knowing which one you are looking at tells you most of what install day will bring.
Server operations. A billing script and a help-desk and ticket system. These are staff tooling rather than player content, and they are the two most likely things here to change how your server is run rather than how it plays.
Player mechanics. A crafting script, a purchasable market, minigame bundles and a vehicle plate customizer. The minigames are infrastructure: lockpicking and hacking skill checks that other resources call, so installing one bundle gives your server a single visual language instead of four different puzzles.
Map content. Two showroom interiors, a house, and road vegetation. Map data cares about no framework at all and will run on an empty server. Vegetation is the one to test carefully, since it streams across the whole map rather than one building.
Vehicles. A lore-friendly police pack. Vehicle content sits below the framework layer, so it installs the same way on ESX, QBCore or Qbox.
Buying from a shelf like this
Check dependencies per listing, not per page. A help-desk script and a showroom MLO have nothing in common except the URL they share, and the only thing this grouping tells you is that these eleven things arrived together.