SNAIL OPS MANUAL

DOCUMENTATION

Current operating notes for the SlimyAI Super Snail tools. This page covers the live web surfaces, the owner-only OCR workflow, and the minimum checks to run before trusting imported club data.

BACK TO HUB

Club Dashboard

Review current roster power, import XLSX snapshots, and open owner-only import history.

Use the dashboard for the latest club roster snapshot.
Use XLSX import when you already have structured roster data.
Use history to confirm previous imports and pushes.

OPEN CLUB DASHBOARD

Screenshot OCR

Upload Manage Members screenshots, review extracted rows, then push confirmed data.

Upload 1 to 10 clear PNG, JPG, or WEBP screenshots.
Upload one metric type per batch: all Power screenshots, then a separate Sim Power batch.
Review extracted names and powers before pushing.
Remove questionable rows instead of pushing uncertain OCR output.

OPEN SCREENSHOT OCR

Codes

Browse active Super Snail codes and source metadata from the public scanner.

Use active scope for current codes.
Check metadata when deciding whether a code needs manual review.
Owner tools can scan and push code updates to Discord.

OPEN CODES

Stats

Track club-level power, member counts, and trend data where the data source is available.

Use stats after imports to verify aggregate changes.
Compare club dashboard rows against stats totals after large updates.
Treat missing values as a data-source gap, not a player result.

OPEN STATS

Access Model

Public

Snail hub, wiki, docs, public codes, public stats links.

Member

Guild list and authenticated dashboard areas.

Leader

Club dashboard and stats surfaces used for roster review.

Owner

Screenshot OCR, import history, pushes, and owner admin tools.

Data Trust Rules

Screenshot OCR is a draft extraction until a human reviews row names and power values.
Regular Power and Sim Power screenshots must stay in separate batches; do not merge those fields by guess.
A Power-only batch preserves existing Sim Power, and a Sim Power-only batch preserves existing regular Power.
XLSX imports are preferred when the source sheet is current and structured.
Pushes should be treated as live data changes. Confirm guild, roster count, and obvious OCR mistakes first.
When OCR and sheet data disagree, keep the original import evidence and check import history before overwriting.