One more (strange) bug in Mission Architect

I found another bug in Mission Architect and this time it will give a bit of work for Doc Aeon.
I tryed to put in a mission a "Defendable Object" goal and, when I tested it, just after I attacked the enemies surrounding the object, a copy of it immediately spawned nearby and was attacked by the enemies. Moreover, even if I defeat all the enemies around them, no ambushes spawn to try to destroy the objects.
I don't know if this problem affects also published arcs, someone can verify it?

I found this bug as well. Popped up in one of my published arcs.

I did some testing and found these things do not affect the bug:

Enemy group
Object type
Triggers set on the object
If the object is rogue or enemy
Removing the objectives, saving the file, then placing a defendable object in the mission again.

It remains broken through all of these changes.

I also found that the system reports the object as being defeated by it's surrounding npc's at the first sign of damage, so the object takes 5 damage, system reports that 'NPC defeated Object; but the object is still alive.

Hmm... someone asked for an arc to play the other night, and I gave them mine. They ended up having to abandon it because of problems with the Defendable Object in the 3rd Mission.

I tested, and could not get the ambush to spawn. I defeated all foes in the room, and the mission still wouldn't end. No idea why.

So, looks like Defendable Objects are broken.

[ ProTip: The banner is a link to art refs!! | The Khellection | The HBAS Repository | Brute Guides (4/16/10) | How To Post An Image - A Quick Guide ]
Biggest Troll on the forums? I'll give you a hint:

I recently (this week) play-tested my arc, "A Spanner In The Works, Part One" (ArcID: 336662) and found that the second mission, "Defend the Comm Node!" suffered from this bizzare behaviour. After successfully defending the one and only Defendable Object in the mission, the mission objective changes to Defeat all enemies (in place so players have to clear the warehouse of mobs who could still endanger the Defendable Object), a second duplicate Defendable Object appears in the only other spawn point in the Tiny map and spawns attackers.

I believe I altered the Required for Mission Completion toggle on a Boss in the mission, switching it off, and switching on the Required for Mission Completion toggle of the Defendable Object. I added the Defeat All Objective and made it necessary for mission completion. Two play-through's later and the problem hadn't been repeated. On a third play-through today I find that actually the problem is still there! So, if Dr. Aeon wants an example arc, it's listed above.

Hey guys, we're aware of the current issue regarding the defendable objects and are working on a solution, but I can't give any ETA on when that will come down the pipe.

I'm noticing a trend where the devs pipe in and acknowledge a problem exists instead of letting multiple threads complaining about a problem to stew for weeks until we see a patch note fixing it.

I like this new approach. Now we just have to wait to see if they follow through.

This is totally irrelevant - but.. what is your picture from, AegisWolf? It's hypnotic.

This bug crippled my DevChoice Laser Moonbase arc for a couple weeks, there.

Now, understandably, bugs not only take a long time to fix but also a long time to work their way into a public build. This is doubly difficult with Going Rogue out there requiring a split codebase. So I can see why it's gonna take awhile.

Rather than wait, I just edited the arc to use a clicky instead of a defendy and requested it re-DC'd. I suggest others do similar, if feasible within your story structures, until the bug is out of your hair. Beats confusing users and getting 1-star ratings left and right.