Change Details

Currently the garrison of an entity ought to be stored seperately in the mapfile as a script. That is doable. However, D1958 allows entities to be created on init, thus when an entity is defined in a map it will create another one on map load (using the entity ID +1, creating havoc). The only proper way of solving this would probably be to define that there is already an entity on the position. This patch aims at fixing that the entities garrisoned in Atlas are stored and (re)garrisoned at init. However, since I am a rather inexperienced C++ programmer, I cannot do this myself :( So help would sincerely be appreciated :) --- See also: - rP16270. - #2984.

Currently the garrison of an entity ought to be stored seperately in the mapfile as a script. That is doable. However, D1958 allows entities to be created on init, thus when an entity is defined in a map it will create another one on map load (using the entity ID +1, creating havoc). The only proper way of solving this would probably be to define that there is already an entity on the position. This patch aims at fixing that the entities garrisoned in Atlas are stored and (re)garrisoned at init. However, since I am a rather inexperienced C++ programmer, I cannot do this myself :( So help would sincerely be appreciated :) --- See also: - rP16270. - #2984. - D2562.

Currently the garrison of an entity ought to be stored seperately in the mapfile as a script. That is doable. However, D1958 allows entities to be created on init, thus when an entity is defined in a map it will create another one on map load (using the entity ID +1, creating havoc). The only proper way of solving this would probably be to define that there is already an entity on the position. This patch aims at fixing that the entities garrisoned in Atlas are stored and (re)garrisoned at init. However, since I am a rather inexperienced C++ programmer, I cannot do this myself :( So help would sincerely be appreciated :) --- See also: - rP16270. - #2984. - D2562.