Source: Love Mac | Software download link: Bounty of One for Mac
I. Detailed Explanation of the Core Interface and Workspace
The main interface of Bounty of One features a clear, functionally partitioned design, primarily divided into the following five areas:
- Top Menu Bar and Toolbar: Includes standard menus such as File, Edit, View, Project, and Window. The toolbar provides shortcut buttons for the most commonly used functions, such as project creation, saving, running, and debugging.
- Left Navigation Panel (Project Resource Manager): Displays all files and folders of the current project (such as scripts, resources, and configuration documents) in a tree structure. You can manage the file structure by dragging and dropping.
- Central Editing and Preview Area: The core workspace of the software. The upper part is the code/configuration editor, supporting syntax highlighting and intelligent suggestions; the lower part is the real-time preview window, allowing you to instantly view the project’s running results.
- Right-side Properties/Inspector Panel: When an element is selected in the navigation panel or preview area, this panel displays its detailed properties (such as size, coordinates, and state variables) and supports direct editing.
- Bottom Status Bar and Output Console: The status bar displays information such as the current line number and encoding. The console outputs project build logs, runtime information, and debugging information, and is a key window for troubleshooting.
II. Complete Workflow: From Creation to Export
Step 1: Create or Open a Project
Method: After launching the software, click “New Project” on the welcome screen, or use the menu bar “File” > “New” > “Project…”.
Location and Shortcuts:
- Menu path:
File > New > Project… - Shortcut:
Command + Shift + N - Open an existing project:
Command + O
In the New Project dialog, you need to select a project template (such as “Basic App”), set the project name, storage path, and initial configuration.
Step 2: Configure the Project and Add Resources
In the left navigation panel:
- Right-click the project root directory and select “New” > “File” to add scripts or configuration files.
- Drag external resource files (such as images and audio) directly into the “Assets” folder in the navigation panel.
Shortcut tips: Create a new file Command + N; rename the selected file Enter.
Step 3: Write code and preview in real time
Write the main logic code in the central editor area. While writing, you can use:
- Code completion: Press
Control + Spacewhile typing to trigger it. - Quick jump: Hold the
Commandkey and click a function/variable name to jump to its definition.
During the writing process, the bottom preview area will refresh automatically (the “real-time preview” mode must be enabled). You can also manually click the “Run” button in the toolbar (shortcut Command + R) to perform a full build and preview.
Step 4: Debug and test
Click to the left of a code line number to set a breakpoint. Start a debugging session via the menu “Debug” > “Start Debugging” (Command + Shift + D).
The program will pause at the breakpoint. At this point, you can view variable values in the bottom console and use the debugging toolbar (continue, step over, step into) to control the execution flow.
Step 5: Build and export the final product
Configure the output format (such as a standalone application or installer), icon, version number, etc. via the menu “Project” > “Build Settings…”.
Export operation:
- Select the menu “Project” > “Build Project…”.
- In the dialog, select the target platform (macOS) and the output directory.
- Click “Build”, and the software will start compiling and packaging; progress and result logs are displayed in the console.
Shortcuts: Build project Command + B; Build settings Command + Shift + ,.
III. Advanced Tips for Common Features
- Multi-cursor editing: Hold the
Optionkey and click at different positions to create multiple cursors for batch editing. - Quick file open: Use
Command + P, enter a file name to quickly locate and open any file in the project. - Code snippet management: Select a commonly used code block in the editor, right-click and choose “Create Snippet”, set a trigger abbreviation for it, and then type the abbreviation to quickly insert it later.
- Version comparison: Right-click a file in the navigation panel and choose “Compare with Saved Version” to intuitively view all changes since the last save.
- Custom workspace layout: All panels (navigation, inspector, console) can be separated into independent windows by dragging their title bars or repositioned to suit different workflows. Layouts can be saved and recalled via “Window” > “Workspace Layout” > “Save Current Layout”.
IV. Common Issues and Solutions
| Symptom | Possible Cause | Solution |
|---|---|---|
| Preview window unresponsive or showing a blank screen | 1. Live preview is not enabled. 2. The main script file path is incorrect. 3. A syntax error in the code is causing an interruption. |
1. Check whether the “Live Preview” button in the toolbar is highlighted. 2. In the project settings, confirm that the “main entry file” points to the correct file. 3. Check the console for red error logs and fix the syntax errors. |
| Build fails with “missing resources” or “insufficient permissions” | 1. Referenced external files have been moved or deleted. 2. The output directory does not have write permission. |
1. In the navigation panel, check the status of resource file links (broken link icons) and relink them. 2. Try changing the output directory to a user directory such as “Desktop” or “Documents”, or grant full disk access permission through System Settings. |
| The software runs slowly and responds sluggishly | 1. The project is too large, and live preview is consuming too many resources. 2. Cache files have accumulated. |
1. Temporarily disable live preview and run it manually only when needed (Command+R). 2. Quit the software, go to ~/Library/Caches/com.vendor.bountyofone (replace vendor with the actual developer name), delete the cache files, and then restart. |
| Custom keyboard shortcuts not working | Conflicts with system or other app keyboard shortcuts. | Go to “Bounty of One” > “Preferences” > “Keyboard Shortcuts”, check for conflicts, and reassign them. |
V. Shortcut Key Summary (Mac Version)
| Function Category | Operation Description | Shortcut Key |
|---|---|---|
| File & Project | New Project | Cmd + Shift + N |
| Open Project | Cmd + O | |
| Save Current File | Cmd + S | |
| Save All Files | Cmd + Option + S | |
| Editing Operations | Undo | Cmd + Z |
| Redo | Cmd + Shift + Z | |
| Find | Cmd + F | |
| Find in Project | Cmd + Shift + F | |
| Code Completion Suggestions | Ctrl + Space | |
| View & Control | Run/Preview Project | Cmd + R |
| Stop Running | Cmd + . | |
| Start Debugging | Cmd + Shift + D | |
| Toggle Full Screen Mode | Ctrl + Cmd + F | |
| Navigation | Quick Open File | Cmd + P |
| Jump to Definition | Cmd + Click | |
| Toggle Sidebar Show/Hide | Cmd + B | |
| Build | Build Project | Cmd + B |
| Open Build Settings | Cmd + Shift + , |
“`








