Roblox running on your device answers only part of the compatibility question. The script, tool version and operating system need matching information of their own. Start by identifying your actual setup and the selected entry, then use the platform section below. Where information is missing, an unknown status is more accurate than a guessed supported badge.
The Roblox App, Lua Script and Executor Have Different Roles
Downloading a File Does Not Run It
The Roblox application runs the game. A Lua script is text containing instructions. An executor is a separate execution environment referred to in script discussions. These roles should not be collapsed into one download. A browser can display, copy or save the text without establishing anything about the later behavior of the script in another environment.
This distinction also helps you interpret success. Seeing a saved file means the download step completed. Seeing a menu means an interface appeared in that particular environment. Neither result by itself proves that fishing, selling and every other option work. The action table provides a reference for describing the step you reached before you start investigating the next one.
| Action | What it does | What it does not prove |
|---|---|---|
| Copy | Places the published script text on the clipboard | That it has run or supports your device. |
| Download Lua | Saves the same text as a Lua file after the wait | That an executor is installed or the file will run. |
| Open Roblox | Starts the game client | That a particular script/executor combination is supported. |
| See a script menu | Shows that an interface appeared in that environment | That every fishing or selling function works. |
Fish It Scripts on Android
Check the Exact Tool and Touch Controls
For Android, identify the actual operating-system setup and the exact tool build mentioned by the source you are consulting. Then read the selected script’s platform notes. A general mobile label leaves too much unspecified to confirm a particular pairing. A screenshot showing a phone-shaped menu is useful for understanding layout, but it is not a compatibility test.
After support information is clear, consider how the menu fits your screen. Touch targets should be reachable, option lists should scroll and a close control should remain accessible. If the interface covers a game action you need, its appearance in a screenshot does not solve the usability problem. Record the specific control and screen state rather than reporting only that mobile does not work.
Fish It Scripts on iOS
Require an Explicit Compatibility Statement
Treat iOS as a separate compatibility question. An Android statement cannot be reused simply because both devices use touch screens. Look for explicit information naming the relevant iOS setup, tool build and selected script. If that pairing is not described, keep the status unknown. This guide does not supply an invented installation package or assume a signing method.
The same separation applies to browser actions. You may be able to read a card, copy text or download a file on an iOS device while having no confirmed execution setup for the script. That is a completed browser task followed by an unanswered compatibility question. Keeping those results separate avoids interpreting a download as a promise that the next stage will work.
Fish It Scripts on PC
Name the Desktop Operating System and Build
On a desktop, write down the operating system rather than using PC as the entire specification. A statement about one Windows setup does not automatically include macOS, Linux or a different tool build. The script entry and the primary information for the execution tool should describe the actual combination you intend to assess.
Keyboard and mouse controls also need practical attention. Can a menu be reached in a narrow window, does a long list remain navigable and is the closing action clear? These are interface questions after the support question, not a replacement for it. A larger screen can make a control easier to see without changing the underlying compatibility of the selected code and environment.
How to Read Delta, Xeno and Solara Mentions
A Brand Name Is Not a Support Matrix
Delta, Xeno and Solara appear in searches and discussions about execution tools. Their names alone are not a support matrix. A useful statement identifies a release, operating system and the script to which it applies. An author’s description should remain attributed to the author; independent verification requires an actual recorded check with a date, configuration and result.
Use the table and preparation checklist before choosing a setup. They keep unknown combinations visible instead of filling empty cells with supported symbols. They also prevent a statement about one function from expanding into a claim about every menu option. For example, a record that only establishes interface visibility would still leave fishing and selling behavior to be checked separately.
| Platform | What must match | Required support detail |
|---|---|---|
| Android | Actual device setup, tool build and selected script | Explicit current support information; otherwise unknown. |
| iOS | Exact iOS setup, tool build and selected script | Independent iOS information, not an Android inference. |
| PC | Named desktop OS, tool build and selected script | The documented OS; no automatic macOS/Linux assumption. |
- Identify your actual operating system.
- Find the exact script entry and its device notes.
- Check the relevant executor build using current primary information.
- Read the script’s key requirement separately from the executor’s.
- Keep unsupported or undocumented combinations marked unknown.
Check the Menu and Choose Your Next Step
Use the Device Notes Before Copying or Downloading
Read the current device notes in the Fish It script catalog before choosing an entry. Then use the small-screen checklist to evaluate the interface information available for that entry. A website’s own responsive layout or color theme says nothing about whether a third-party in-game menu supports the same device.
Copy transfers the published text immediately; Download offers the same text as a Lua file after the 15-second wait. If either browser action fails, the help guide provides a separate route to diagnosis. If your question concerns what an option is supposed to do, read the automation guide. Neither a file extension nor a tool name settles both questions.
- Buttons can be reached without overlapping the game controls.
- Labels remain readable instead of being clipped.
- Long option lists can be scrolled.
- Closing or moving the menu has a clearly described control.