Small tools, honestly scoped.

What it does

• Parses ensure/start lines you paste and lists them in the order the server would actually process them.
• Flags a small, named set of known prerequisite relationships (oxmysql, ox_lib, the three framework cores, vf_core) when a likely dependent starts first.
• Flags duplicate resource entries and commented-out lines so nothing is silently ignored without you noticing.

What it does NOT do

• Does not read your actual resource folders, fxmanifest files, or convars — only the text you paste.
• Does not know about resources started from a separate exec'd config file it was never shown.
• Does not know every resource's real dependencies — only a small, named list of well-known ones.
• Does not guarantee your server will start cleanly even with zero findings.

What it does

• Adds the idle and active milliseconds you enter for each row into running totals.
• Shows what share of a 16.67ms (60fps) frame those totals represent, as arithmetic.
• States Vice Drip's own idle/active engineering target next to your numbers, clearly labeled as our target, not a verdict on yours.

What it does NOT do

• Does not measure anything — it has no connection to your server and never runs resmon itself.
• Does not know your player count, your other resources, or your hardware, all of which affect real frame time.
• Does not declare your numbers good or bad against any industry threshold — none is published here.

What it does

• Scans pasted text against a named list of patterns that commonly indicate secrets or personal data.
• Produces a redacted copy with each match replaced by a labeled placeholder, ready to select and copy.
• Explains, per finding, what the pattern usually is and why it is worth stripping before you share the text.

What it does NOT do

• Does not guarantee the redacted copy is safe to post — it surfaces likely secrets, it does not certify their absence.
• Does not send, log, or store anything you paste; everything happens in memory in your browser tab.
• Does not replace rotating a credential that was actually exposed — redacting text after the fact does not undo a leak.

What it does

• Cross-checks the framework, database, inventory, and target you select for named patterns that commonly need a bridge or are worth a second look.
• Flags specific conflicts — a target system that doesn't match your framework's common default, an inventory from a different framework's ecosystem, or an escrowed resource that cannot be patched later.
• Suggests an install sequence and a testing checklist tailored to the exact stack you selected.

What it does NOT do

• Does not read the actual resource you're installing — it only reasons from the stack choices you select here.
• Never states a combination is "compatible": findings are phrased as likely, worth inspecting, or commonly needs a bridge, never a guarantee.
• Does not know the resource's real dependency list, its actual code, or its author's tested-version matrix.
• A "likely works" result is not a certification that nothing will break.

What it does

• Turns the systems you tick into a single checklist, ordered the way they commonly need to be planned and installed.
• Lists the integration questions each choice forces — the decisions that connect one category to another — plus a plain-English integration-risk note per layer.
• Names a Vice Drip product where one maps to a category you ticked, always with the same honest, hedged status.

What it does NOT do

• Does not know your actual server, its current resources, or your player count — it only orders the categories you tick.
• Does not recommend a specific third-party resource for any category — that choice, and the diligence behind it, stays yours.
• Naming a Vice Drip product next to a category is not an offer: nothing here is purchasable, no runtime proof is published for any of them — pending Shadow bench — and this page is a planning reference, not a storefront.

What it does

• Groups a pre-flight checklist into before you download, before you install, install, first boot, verify, and rollback readiness, with a running progress count.
• Lets you tick items as you go and copy the whole checklist — with your progress marked — as plain text to paste into your own notes.
• Keeps every tick in this page's own memory for the duration of your visit, nothing more.

What it does NOT do

• Does not save your progress between visits — there is no localStorage, cookie, or account behind it, so refreshing or closing the tab clears it.
• Does not install, download, or touch anything on your server — it is a checklist, not an installer.
• Does not know which items apply to your specific resource — some rows (an escrow manifest check, for instance) only matter if the resource you're installing is actually escrowed.