Skip to content

[Workaround/Fix] Comprehensive Solution for Player Persistence "Clone" Bug | ARMA 3 + ALiVE #822

@FNRennier

Description

@FNRennier

SOLVED: Guide to fix the "Clone" (ALiVE) persistence and reappearance bug

The End of Clones in ARMA 3 + ALiVE Mod: The Definitive Guide

Author: =FN=Rennier (Brazil)

Hello everyone! I bring to the Arma 3 community the definitive solution for the character duplication problem and perfect persistence using the ALiVE mod.

Image

🛑 The Problem: The Clone Paradox

Many editors using ALiVE to create persistent missions (where you save and continue from where you left off) face a devastating bug. When loading a save and respawning, you find a copy of your character standing at the base or at the last saved location. This "clone" joins your squad, breaking immersion.

It is not just a visual error; it is a failure in the "soul transfer" between the saved data and the physical unit on the map. After scouring global forums (Bohemia, Reddit, Discord), we found that cleanup scripts (deleteVehicle) only treat the symptom. We have found the cure for the disease.

🎯 The Goal

We want three things working in harmony:

Zero Clones: No duplicate units at the base.

Real Persistence: The player must respawn exactly where they saved the mission, not restart at the base every time.

Squad Integrity: Your group's Bots (AI) must come with you, keeping their equipment (loadout) and position.

💡 The Solution: "Physical Synchronization"

The common mistake is relying solely on ALiVE modules to "spawn" units or leaving the player slot empty/virtual. Stability requires that units exist physically in the editor and are "introduced" to the module.

Step 1: Mandatory Physical Presence

Do not use Virtual AI to spawn your own group.

Place the Player Avatar physically on the map (Editor).

Place the Squad Members (AI) physically on the map, already grouped to your player.

Step 2: The Synchronization (The Secret)

This is the secret that many tutorials ignore.

Create a Sync line by right-clicking on your Avatar (Leader) and connecting it directly to the ALiVE Virtual AI System module.

Mandatory: Do the same for all squad members (AI). Each soldier in your group must have their own sync line connected to the Virtual AI System module.

Why does this work? By syncing, you tell ALiVE: "This physical doll HERE IS the data you have saved." The system then merges the save with the physical doll instead of creating a new one.

🛡️ Step 3: The "Life Insurance" (Fixed Base Respawn)

To ensure the respawn system works if you die (and not just when loading a save), and to avoid spawning in the middle of the ocean ("edge of the map") if something fails, it is mandatory to have a fixed point at the base.

  1. Creating the Marker

In the Editor, go to the Markers tool (Flag icon or F6).

Choose any icon (it can be the blue "Respawn" or an Empty icon).

Click on the map exactly where you want the soldier to spawn inside the base (in the barracks, tent, etc.).

  1. Configuring the Variable (Essential)

Double-click the marker you just created.

In the Variable Name field, you MUST write exactly:

respawn_west (If you play as BLUFOR/NATO).

respawn_east (If you play as OPFOR/CSAT).

respawn_guerrila (If you play as Independent/AAF).

Note: The name respawn_west is a "master key." When you die, the game automatically looks for this marker. It is your safe ground.

  1. Lobby and Attributes Settings

Now, go to the top bar of the Editor under Attributes > Multiplayer and configure:

Enable AI: Uncheck this option (to prevent bots from taking over slots of disconnected players).

Respawn: Change to "Custom Position".

Rules: Check the box "Select Respawn Position".

Respawn Delay: Set it to 20 seconds (00:00:20).

🆘 Step 4: The Regroup Trigger (Radio Teleport)

Even with correct synchronization, Arma 3 can occasionally "forget" the position of bots when loading a save, leaving them stuck at the base while you are on the battlefield. We created a safety mechanism via Radio to fix this instantly.

How to create in the Editor:

Create a Trigger: Go to F3 (Systems/Triggers) and place a trigger anywhere on the map.

Text: Type Regroup Squad (This will appear in your radio menu).

Activation: Change to Radio Alpha.

Repeatable: Check this box ✅.

On Activation: Copy and paste exactly the code below:

Snippet de código

{
if (!isPlayer _x) then {
_x setPos (player getPos [2, random 360]);
};
} forEach units group player;

What does this code do?

It checks all members of your group. If the unit is not a human player (i.e., if it is a bot), it teleports them to a random position 2 meters away from you. This brings your squad back instantly and prevents them from spawning "inside" you, preventing collision explosions.

How to use in-game: If you notice your squad has disappeared: Press 0, then 0 again, and select "Regroup Squad." Your soldiers will appear around you, ready for combat.

✅ Final Result

When joining the server with these settings:

The system loads your ALiVE persistence.

You wake up exactly where you left off (in the woods, in the city, etc.).

Your squad is by your side (or can be called via radio).

Zero Clones at the base.

Arma 3 is complex, but with "Physical Synchronization" and the Fixed Safety Marker, persistence works like magic.

⚠️ Critical Warning: Squad Permadeath

It is important to remember that when using this physical persistence system, your squad members (AI/Bots) have only one life.

Unlike you, who relies on the respawn_west marker to return, if a soldier in your group dies in combat, ALiVE will save this "dead" state.

They do not respawn with you at the base.

They do not reappear when reloading the save.

If you lose your entire squad, you will have to continue alone.

The only way to get them back is to restart the mission from scratch (Wiping the save on the server/ALiVE). Take care of your men!

Good game!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions