Bloody WorkShop 8 Macros: How to Install, Import and Configure Them

Choose WorkShop 8, Bloody 7, or Bloody Esports by model

A successful installation is not proof that the editor supports the connected mouse. Read the model code from the underside of the device and look up that exact model on Bloody’s official download page before following any button or macro instructions.

Bloody’s global pages describe WorkShop 8 as the upgraded Bloody 7 generation, but regional model lists and supported functions can differ. Treat the exact model page and the controls visible in your installed build as the deciding evidence.

Install or upgrade Bloody WorkShop 8 without losing the working state

Use the manufacturer’s current download, close other mouse editors, and make the first launch a detection test rather than an immediate profile rewrite. Menu wording can change between releases, so follow the function of each control as well as its label.

• Download from the model page. Avoid repacked installers. Confirm the publisher, release information, Windows requirements, and the mouse series named on the page.
• Create a before-state record. Capture the current device name, profile, button map, sensitivity, polling rate, lighting, and any active Core or programming mode.
• Connect the mouse directly. During installation and the first profile write, use a stable computer USB port and let Windows finish device setup.
• Finish installation before importing. Restart only when requested, then open WorkShop 8 and verify that the correct mouse and its real controls appear.
• Switch to Full Key Programming deliberately. Use this mode only after the neutral layout is documented; it exposes the programmable button workflow needed for assignments.
• Keep a recovery control. Leave one ordinary profile or safe button available so an incorrect loop or primary-button remap can be stopped immediately.

Create a clean game folder in Macro Settings

WorkShop 8 organizes imported content inside its own library. A separate folder for each application and revision makes assignments easier to identify and prevents two similarly named files from being confused.

1. Open Macro Settings.

   Enter the macro-management area after the correct device and programming mode have been confirmed.

2. Select the Oscar III library area.

   Use the library or macro tab shown by your build; translated releases may use a slightly different label.

3. Choose New Game.

   Create a container for one application or test purpose instead of placing every file in a generic folder.

4. Name the folder clearly.

   Include the application and revision, for example “Editor shortcuts — test 1”, then confirm the name.

5. Open the new folder.

   Make sure its name is selected before importing so the file does not land in another profile’s library.

Treat the program’s library as the source of truth. Manual edits inside an undocumented installation folder can be ignored, overwritten during an update, or attached to the wrong language-specific library.

Import an external macro into the WorkShop 8 library

Prepare the actual macro file in a clearly named folder before opening the import dialog. An archive is only a delivery container; extract it, scan it, read any setup notes, and reject unexpected executable files.

1. Select External File.

   In Macro Settings, open the external-file source and browse to the extracted macro rather than selecting the ZIP or RAR archive.

2. Inspect the selected item.

   Confirm its filename, extension, intended application, trigger description, and any required in-app key bindings before transfer.

3. Transfer it into the program library.

   Use the transfer arrow or equivalent command to move the item into the selected game folder in the library column.

4. Confirm the library result.

   WorkShop 8 may not show a large success notice. Verify that the imported name is visible in the destination folder and press OK to finish.

5. Preserve the original file.

   Keep the untouched download and a separate working copy so later timing edits can be compared or rolled back.

Assign the imported macro to a mouse button

Importing fills the library; it does not activate the physical mouse control. The second stage happens under Buttons in Full Key Programming, where you choose both the trigger and the playback style.

1. Open Buttons.

   Confirm that Full Key Programming is active and that the screen diagram matches the connected mouse.

2. Choose a test profile.

   Use a separate programmed profile—commonly Profile 2, 3, or 4—while retaining a neutral layout for recovery.

3. Select a non-primary button.

   Begin with an easy-to-identify side control so ordinary left click remains available during diagnosis.

4. Choose the imported library item.

   Open the action list, enter the game folder, and select the exact macro revision you just verified.

5. Set the intended trigger style.

   Decide whether the control runs the macro directly or toggles a mode used by another button. Do not guess from the file name.

6. Press APPLY and wait.

   Keep the mouse connected until the editor reports or visibly completes the profile write.

7. Test one controlled cycle.

   Use a harmless window, observe start and stop behavior, then return to the neutral profile before changing timing or repetition.

Understand profiles and the 1, 3, and N mode buttons

WorkShop 8 can expose ordinary programmable buttons and model-specific mode controls in the same editor. Their availability and names are not universal, so treat the screen for your mouse as authoritative.

Do not assume that Profile 1, Profile 2, or an N button behaves identically on another Bloody model. Document the working screen, physical trigger, and selected macro together.

Create or tune your own WorkShop 8 macro safely

A maintainable macro has one permitted outcome, a known trigger, balanced press and release events, and a visible end. Plan the sequence before recording so accidental input does not become part of the final file.

1. Describe one result in plain language.

   Write what should happen and in which application state; split unrelated tasks into separate macros.

2. List every event.

   Record each press, pause, release, click, and wheel action in order before optimizing timing.

3. Create a short first revision.

   Use the editor available in your WorkShop 8 build and enter only the minimum actions needed for one complete cycle.

4. Audit press/release pairs.

   Remove accidental duplicates and make sure no key or button remains logically held at the end.

5. Tune one delay at a time.

   If the target misses an event, adjust the pause around the first failure rather than accelerating the entire sequence.

6. Save a new revision.

   Keep the last working file, profile screenshots, and a note with mouse model, software build, trigger, mode, and date.

Speed is not the same as reliability. A slightly slower finite sequence that behaves consistently and can be stopped is preferable to an aggressive loop whose state is unclear.

Bloody WorkShop 8 macro does not work: focused checks

Diagnose in order: exact model, editor build, device detection, library import, active profile, physical trigger, privilege level, and target rules. Reinstalling first can erase the evidence that identifies the broken layer.

For the original screenshot-oriented sequence in the matching language, compare the TopMacro WorkShop 8 setup guide.

If you need a prepared macro for a supported mouse and application, review the EasyMacro catalog and verify the listed editor, model, trigger, and setup requirements before purchase.

Use mouse automation only where the current rules allow it

Bloody WorkShop 8 is official device software, but that does not make every imported sequence acceptable in every game. Publishers, servers, leagues, and tournaments can restrict repeated input, multi-action bindings, recoil-related assistance, unattended play, or other automation.

Check the current policy for the exact game, server, mode, and event before enabling a macro. No vendor, file seller, or hardware manufacturer can guarantee that a configuration is “undetectable” or safe from future enforcement.

Keep manual control available, begin with a finite test, and use the smallest sequence needed for an allowed purpose. Technical operation and permitted use are separate questions; both must be satisfied.