A method can be carefully reviewed, remain in a catalog, and still disappear from a live list of recommendations. That is not a data error. In my OSRS money-maker finder, it is often the correct result.
The catalog and the recommendation list answer different questions. The catalog says that a method has been examined and has usable requirements, item inputs, outputs, and action-rate assumptions. The live list asks whether that method fits this player right now.
The first test is eligibility. A members-only route should not appear for a free-to-play player. A Wilderness route is excluded when the player says no to Wilderness activity. Skill requirements, starting cash, and the preferred amount of attention can remove other methods.
The second test is the current market calculation. Inputs are valued at the live high price, outputs at the live low price, and Grand Exchange tax is deducted. If the result is zero or negative, the method is not recommended even though its reviewed record stays in the catalog. The method can return when the prices make sense again.
Keeping these two layers separate matters. Deleting an unprofitable method would erase useful reviewed information. Showing it as a recommendation would suggest that a historical review overrules the current numbers. Neither choice is honest.
This is also why the empty state is useful. When OSRS Money Makers finds no match, it means every reviewed option failed at least one declared condition or the current profit test. The player can change a real constraint, such as available cash or Wilderness preference, instead of being handed a filler suggestion.
The system is still an estimate. Live prices move, orders may fill slowly, and a player may not sustain the reviewed action rate. But a method that vanishes has at least failed a visible rule, not an unexplained score.
For recommendation software, exclusion logic deserves as much attention as ranking logic. A smaller list with defensible omissions is more useful than a large list that never says no.
