Aplok Guns 1.1.8: Bedrock Version and Setup Guide

Minecraft Bedrock · Combat add-on

Aplok Guns builds a survival-oriented military layer around craftable firearms, attachments, armor, explosives, and first-person presentation. Its current source record also contains a version mismatch that players should not ignore: CurseForge calls the release v1.1.8, while the downloadable filename displayed for the same file contains v1.8.8. Treat those as two recorded labels, not an invitation to guess which one the creator meant.

The exact release record

The title and filename belong to the same exact CurseForge file record, so neither should be silently corrected. When asking for support, include file ID 7306900 along with both visible version strings. That identifies the object more reliably than saying “latest Aplok.”

Current 26.x compatibility is not established

The release lists these discrete Bedrock builds: 1.21.80, 1.21.81, 1.21.82, 1.21.90, 1.21.92, 1.21.93, 1.21.94, 1.21.100, 1.21.101, 1.21.111, 1.21.114, 1.21.120, 1.21.121, 1.21.122, 1.21.123, and 1.21.124. It does not display a 26.x label.

A successful import on a newer client would not prove the gun scripts, animation timing, attachment state, crafting, multiplayer authority, or removal path still work. Players on a current 26.x build should treat this release as unsupported until the creator publishes a compatible record or a controlled test produces a narrowly documented result.

What changed in this release

The creator describes a major rendering and firing rewrite. Gun visuals now use attachables and “true 3D items” instead of player-entity-based rendering. Firing was rewritten around time rather than frame-dependent animation delays, although the changelog itself marks that work as in development.

Five weapons are named in the notes: AK-74, AKM, AKs-74u, M1014, and ParaFAL. The release also adds 6B13 and BNTI Gzhel-K armor, an ACOG sight, Predator V4 support for pistols, sight support for the M249, item groups for ammunition and attachments, item descriptions, and first-person 3D grenades.

Balance changes matter just as much as the new catalog. The changelog reduces the M249's power, lowers the sneaking damage bonus, softens the silencer penalty, and changes the attachment workflow to use the necessary attachment item instead of a blueprint. A guide for an older build can therefore teach the wrong damage or assembly behavior.

One .mcaddon is visible, but the package is still unresolved

CurseForge displays a single .mcaddon file and says there are no additional files on that record. Other creator material has described a ZIP route that exposes separate BP and RP packs. Because MineBrush did not acquire or inspect file 7306900, it cannot prove whether the current .mcaddon bundles every required component, whether its “BP” filename is only a naming artifact, or whether another step is expected.

Use this fail-closed rule: if the creator's current project instructions and the exact file record do not agree on what to import, pause. Do not rename the archive, combine files from another release, or borrow a resource pack from a mirror. A clean install begins only when the package shape is unambiguous.

A controlled evaluation route

1. Confirm that the intended Bedrock build is explicitly listed. For 26.x, stop unless the creator adds support or you accept a disposable unsupported test.
2. Record project ID 1125776, file ID 7306900, the release title, displayed filename, size, and acquisition date.
3. Read the current Custom License and creator installation notes before retaining or sharing any file.
4. Import only through the creator project route. If Minecraft exposes separate behavior and resource components, record both exact names before activation.
5. Create a fresh combat-test world. Do not use a Realm, community map, or only copy of a survival world.
6. Test one weapon, one attachment, one armor item, one explosive, and one crafting route before expanding the loadout.
7. Close Minecraft completely, reopen the world, and verify every retained item and attachment state again.

Prove the rendering rewrite with different skins

The creator says default Minecraft model rendering now supports slim, default, and Marketplace skins, but also documents a known item-pivot misalignment with Marketplace skins. Test at least one default and one slim model in first and third person. If your group uses Marketplace skins, include one in the acceptance test and capture the exact item and camera angle when the pivot shifts.

The old experimental leaning system was removed because the creator considered it dysfunctional and below the project's standards. Its absence is intentional in this release. Do not troubleshoot a missing lean control as an installation failure.

Separate firing logic from frame rate

The move to time-based firing is meant to remove FPS-dependent fire rates and animation delays. That is a creator-stated design goal, not a MineBrush benchmark. Test it by firing the same weapon at a fixed target under a stable scene, then repeat after deliberately increasing visual load. Record shot cadence, animation completion, hit registration, reload behavior, and input feel separately.

Do not infer “optimized” from a smaller particle cloud. The changelog reduces bullet-impact particles and smoke opacity, but no FPS, frame-time, battery, heat, memory, or network result is supplied. A low-end phone and the multiplayer host are the useful machines to measure.

Attachments need their own regression sheet

Because the attachment system changed, verify acquisition, application, removal, model alignment, sight picture, reload, death, reconnect, and world reopen for one representative gun. Repeat with the ACOG and the M249 sight support called out in the changelog. An attachment that looks correct for one session but disappears after reconnect has not passed.

Keep ammo groups and crafting separate from the visual test. If a gun renders but cannot accept its intended ammunition or recipe, identify that as a progression fault rather than calling the entire add-on “working.”

Multiplayer and community rules

Aplok Guns changes combat balance, visibility, explosives, and equipment progression. Before a shared-world trial, define whether friendly fire, explosives, armor, stealth smoke, and attachments are allowed. Give joining players the exact release record and require a resource-delivery check before combat starts.

Run the smallest multiplayer test with a host and one joining client. Check weapon models both ways, shot registration, reloads, dropped items, death, reconnect, and saved attachment state. Realms and dedicated servers were not independently verified, so a local host pass cannot be generalized.

Conflict and rollback boundaries

Model, animation, player, UI, item, projectile, and combat packs are the highest-value conflict candidates. Add them back one family at a time after Aplok works alone. A visual collision with a Marketplace skin is not necessarily the same defect as a broken projectile or crafting recipe.

Before removal, return add-on equipment to a disposable test area, clear active explosives and projectiles, save, and export the world. Deactivate every component that Minecraft shows, restart, and inspect inventories, entities, recipes, and logs. Exact cleanup behavior is unknown because the file was not examined.

Troubleshooting by the earliest symptom

Rights, media, and download boundary

CurseForge labels this project Custom License. That is not blanket permission to mirror the .mcaddon, alter it, or republish creator screenshots. MineBrush points to the creator project and exact record while retaining no artifact.

No real Aplok package, MineBrush runtime capture, or locally retained creator screenshot was found. The existing page cover is generated editorial artwork and must not be presented as proof of the current weapon models.

Primary sources

• Aplok Guns creator project
• Exact file 7306900

Source metadata was rechecked August 24, 2026. Recheck the project before importing; a new release should replace both the compatibility table and the package-shape warning only when its exact record supports the change.

For more tested setup guides, browse the Minecraft Bedrock add-ons hub.