Page MenuHomeFeedback Tracker

Explosion in objects with names (z1,z2...) conflict with names
Closed, ResolvedPublic

Description

I find that object called z1,z2 and so on explodes at 20 seg to put on the map.

I create a mission file to show this extrange behaviour.

This showcase ;) show how tree trigris called z2,z3,z4 explodes 20 seg. after the missions begins.

A fourth trigris called "test" dont explodes.

{F23758}

Details

Legacy ID
93577060
Severity
None
Resolution
No Bug
Reproducibility
Always
Category
Scripting

Event Timeline

djotacon edited Steps To Reproduce. (Show Details)Apr 21 2014, 8:02 AM
djotacon edited Additional Information. (Show Details)
djotacon set Category to Scripting.
djotacon set Reproducibility to Always.
djotacon set Severity to None.
djotacon set Resolution to No Bug.
djotacon set Legacy ID to 93577060.May 7 2016, 6:27 PM
djotacon added a subscriber: djotacon.

Workaround: to avoid name conflict use name convention with more than 5 letters or avoid use name convention like "z1,z2,z3...etc". Use Targetone, Targettwo...etc instead.

Maybe z1, z2, z3...etc explode after 20 seconds because you have a trigger in mission that setDamage to them after 20 seconds?

class Item2

		{
			position[]={25733.234,12.011079,23427.238};
			a=0;
			b=0;
			interruptable=1;
			age="UNKNOWN";
			name="destructor";
			expCond="time > 20";
			expActiv="z1 setdamage 1; z2 setDamage 2; z3 setDamage 1; z4 setDamage 1";
			class Effects
			{
			};
		};

Yep you are right.

I have had several conflicts with names in some respawn functions that I believed were related.

Case solved.

MadDogX added a subscriber: MadDogX.May 7 2016, 6:27 PM

Mass closing tickets marked as resolved more than 1 month ago.

If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.