u/ethanjamescolez

I made a small Task Bar Hero Gear drop finder because the question "where does this item drop?" usually needs more than one number.

The tool starts with an exact obtainable Gear record, then shows its published box source, stage route, difficulty, and Base, Hunter, Slayer, or combined scenario labels. The intent is to make the source trail easier to check before spending time in a run.

The honest limitation is that the catalog can be incomplete, delayed, or incorrect. It does not promise a universal best route or a guaranteed drop, and player-specific clear time belongs in a separate observation layer.

I would especially like feedback on which field a player would verify first: the box, the stage, or the scenario label.

Normally, the “Active users per minute” metric is quite stable with little fluctuation. Today, however, the data suddenly dropped, even down to zero. I thought there was something wrong with the site, or that it had been penalized by Google.

https://preview.redd.it/zk8g99rydzih1.png?width=1776&format=png&auto=webp&s=65a0456b4f1fe11ab27008d8799ef3923de185ce

However, half an hour later, the traffic came back and was even higher than usual.

https://preview.redd.it/qzxq9ff9ezih1.png?width=1484&format=png&auto=webp&s=f0c04e0adbabc69c99d28d32320c42c8274f27de

Another half an hour after that, there were “spikes” (an unusually high bar every 5 minutes).

https://preview.redd.it/kx7ip32mezih1.png?width=1438&format=png&auto=webp&s=9cf4b56c3dc300b998a440a816cb40ca6c97ca38

What kind of signal is this supposed to be sending?

I made a small Task Bar Hero Gear drop finder because the question "where does this item drop?" usually needs more than one number.

The tool starts with an exact obtainable Gear record, then shows its published box source, stage route, difficulty, and Base, Hunter, Slayer, or combined scenario labels. The intent is to make the source trail easier to check before spending time in a run.

The honest limitation is that the catalog can be incomplete, delayed, or incorrect. It does not promise a universal best route or a guaranteed drop, and player-specific clear time belongs in a separate observation layer.

I would especially like feedback on which field a player would verify first: the box, the stage, or the scenario label.

I built a small game-wiki drop finder and I am looking for testers who can check whether the lookup path matches real farming questions.

The current flow is:

1. select an exact obtainable Gear record
2. inspect the published box source and stage route
3. compare difficulty and Base, Hunter, Slayer, or combined scenario labels

I am looking for people who can try a few known Gear records and tell me whether the evidence is clear, whether a route or label is missing, and which limitation needs to be more visible. The catalog may be incomplete, delayed, or incorrect, so this is a request for concrete verification rather than generic launch feedback.

I have been building a small game-wiki tool around a question that sounds simple but keeps exposing a product-modeling problem: a player knows the exact Gear they want, but the useful answer is a chain of evidence, not just a drop percentage.

The data model I keep coming back to is:

1. confirm the exact obtainable Gear record, including rarity, level, and variant
2. follow it to the named box source
3. keep stage and difficulty beside that relationship
4. label Base, Hunter, Slayer, or combined scenario values instead of flattening them
5. store account clear time and repeatability as separate observations

The product lesson is that catalog evidence and player-specific farming results should not be presented as the same kind of truth. A catalog can be incomplete or delayed, displayed percentages are not guaranteed outcomes, and a route that is efficient for one build may not be efficient for another.

I am curious how other indie builders handle this boundary: when your product combines a source catalog with user observations, what have you found useful for keeping the evidence chain clear without turning the result into an overconfident ranking?

I made a Spanish-first AI text and document review tool because I wanted the workflow after "run the detector" to be easier to question.

What I actually needed was:

1. Paste 300 to 100,000 characters or review text extracted from a supported document.
2. Run a first-pass AI-writing signal review.
3. Read the verdict, risk level, AI-generated score, likely-human score, and evidence strength together.
4. Inspect sentence-level highlights instead of relying on one overall number.
5. Copy the report summary or export a printable report for manual review.

The honest limitation is that the report is a probability signal, not evidence that identifies the author, proves plagiarism, or establishes misconduct.

If anyone wants context, I can share the link in the comments.

I made a Spanish-first AI text and document review tool because I wanted the workflow after "run the detector" to be easier to question.

What I actually needed was:

1. Paste 300 to 100,000 characters or review text extracted from a supported document.
2. Run a first-pass AI-writing signal review.
3. Read the verdict, risk level, AI-generated score, likely-human score, and evidence strength together.
4. Inspect sentence-level highlights instead of relying on one overall number.
5. Copy the report summary or export a printable report for manual review.

The honest limitation is that the report is a probability signal, not evidence that identifies the author, proves plagiarism, or establishes misconduct.

If anyone wants context, I can share the link in the comments.

I have been working on a small AI text and document review workflow, and the part I keep second-guessing is how much uncertainty to put directly in the main report.

The tempting version of an AI detector is simple: show one score and make the result feel decisive. I do not think that is the responsible version.

The workflow I kept is narrower:

1. Paste 300 to 100,000 characters or review text extracted from a supported document.
2. Run a first-pass AI-writing signal review.
3. Read the verdict, risk level, AI-generated score, likely-human score, and evidence strength together.
4. Inspect sentence-level highlights instead of relying on one overall number.
5. Copy the report summary or export a printable report for manual review.

The constraint is also important:

AI-detection results are probabilistic, can include false positives and false negatives, and should not be used to identify an author, accuse someone of misconduct, or state with certainty that AI wrote the text.

I am interested in feedback on one thing in particular: when you build or evaluate AI-review tools, what makes uncertainty feel useful instead of buried in disclaimer text?

I built a Spanish-first AI text and document review workflow because I kept seeing the same problem: detector scores are hard to interpret when they are shown as one confident-looking number.

I am looking for a small group of people who actually review Spanish or English drafts, classroom writing, editorial copy, research excerpts, or longer documents and can give practical feedback on the review flow.

What the current workflow does:

1. Paste 300 to 100,000 characters or review text extracted from a supported document.
2. Run a first-pass AI-writing signal review.
3. Read the verdict, risk level, AI-generated score, likely-human score, and evidence strength together.
4. Inspect sentence-level highlights instead of relying on one overall number.
5. Copy the report summary or export a printable report for manual review.

What I would love feedback on:

• does the report make uncertainty clear enough?
• are the sentence highlights useful for deciding what to inspect manually?
• is the copy/export report flow useful for a reviewer?
• what feels missing versus intentionally out of scope?

Important limitation: AI-detection results are probabilistic, can include false positives and false negatives, and should not be treated as proof of authorship, plagiarism, misconduct, or definitive AI use.

If you regularly work with this kind of material and want to try it, I can share the link in the comments.