Bloody 7 Macros: How to Install, Configure, and Create Them

Choose Bloody 7, WorkShop8, Bloody Esports, or Oscar correctly

The product name alone does not identify the required application. Find the model code on the underside of the mouse, search for that exact code on Bloody's official download page, and use the package offered for it. This prevents the common situation in which a utility installs successfully but never detects the device.

Bloody's current product pages describe WorkShop8 as the upgraded version of Bloody7, but that does not make every older device identical. Preserve a functioning installation until the replacement has recognised the mouse and reproduced the controls you need.

Prepare a reversible setup before importing anything

A few minutes of preparation make recovery much easier than guessing which setting changed. Connect the mouse directly to the computer, let Windows finish recognising it, open the vendor utility, and confirm that the model shown on screen matches the device in your hand.

• Save the current state. Export the profile if the application provides that command and capture screenshots of button assignments, CPI, report rate, and active Core mode.
• Create a test profile. Do not overwrite the only layout that already works.
• Extract the download. Work with the actual macro files, not a ZIP or RAR archive.
• Read the supplied notes. A sequence may depend on a particular application setting, key binding, or playback style.
• Plan an exit control. Leave one normal profile or button that can stop repetition and restore standard behaviour.

Understand .mgn and .amc files before adding them

Macro packages for older Bloody and A4Tech utilities commonly contain .mgn or .amc files. Treat the extension as a routing clue, not proof that the file is safe or compatible. Obtain files from a source you trust, scan the archive, and reject installers or scripts that are unrelated to the mouse editor.

On many classic English installations the library is below C:\Program Files\Bloody7\Data\Mouse\English\ScriptsMacros\GunLib\. Your drive, installation directory, language folder, or software generation may differ. Use the folder opened or referenced by your own application rather than creating a guessed path.

Import an existing macro into the Bloody 7 library

Classic Bloody 6/7 builds often organise macro content under Headshot. Interface wording varies, so follow the purpose of each step if your build uses a slightly different label.

1. Verify device detection.

   Open Bloody 7 and wait until the correct mouse appears. Importing into an empty editor is pointless if the driver has not attached to the device.

2. Create a dedicated category.

   Add a new game or library folder with a clear name. Keep unrelated profiles and versions separate.

3. Add the compatible file.

   Copy an .mgn file into that library, or use the M-MACRO/import command for an .amc file when your build exposes it.

4. Return and refresh.

   Reopen the category or restart the utility if the list was already cached before the file arrived.

5. Open the sequence.

   Check the name, event order, pauses, and intended trigger. Never assign an unfamiliar sequence without reviewing it.

6. Save with APPLY.

   Wait for the application to finish writing the profile; disconnecting the mouse during this stage can leave the assignment incomplete.

Create a new Bloody 7 macro instead of importing one

When the utility offers Oscar Macro, M-MACRO, or a comparable editor, build the shortest sequence that performs one clearly defined task. A compact macro is easier to audit and less likely to fail when the target application responds slowly.

1. Write the action on paper first.

   List each press, release, click, wheel event, and pause in the intended order.

2. Create a blank item.

   Name it with the application, purpose, and revision, for example “Editor — insert template — v1”.

3. Record one clean pass.

   Start deliberately, perform only the planned inputs, and stop immediately after the final event.

4. Inspect press/release pairs.

   Remove accidental duplicates and make sure a held key or mouse button has a matching release event.

5. Use realistic delays.

   Begin conservatively. If one stage is skipped, increase the pause around that stage rather than speeding up the whole sequence.

6. Save a new revision.

   Keep the last working version until the edited one has passed several controlled tests.

Assign the macro without losing normal mouse control

Open the button or Core assignment screen, select the physical control, choose the prepared macro and its playback behaviour, then apply the profile. Classic layouts may show 1-Key, N-Key, and 3-Key controls; which buttons accept macros depends on the model and enabled Core mode. Do not assume that a setting from another mouse will be available on yours.

Test a single playback first in a text editor or other non-critical application. Add repetition only after the base sequence is predictable. If a macro changes the left button, verify the neutral profile before opening any program where an unintended click could matter.

Bloody 7 macro problems and focused checks

Use macros within the rules of the application or game

A vendor utility does not grant permission to automate every task. Games, servers, leagues, tournaments, and other services define their own limits, and those rules can change. A sequence that combines gameplay actions, repeats input, or removes a timing challenge may be prohibited even when the mouse officially supports macros.

Check the current policy for the exact game and mode before use. Safer contexts include desktop productivity, accessibility, creative tools, and offline testing where automation is expressly allowed. Avoid unattended loops and never rely on claims such as “undetectable” or “zero ban risk”.

Technical reliability and acceptable use are separate questions. Keep manual control available, use the smallest necessary sequence, and stop if the target behaves differently from the controlled test.