ZDoom

I saw nuh-SING!

As far as the bugs forum is concerned there is no unofficial build. ;)

I think this is actually even fixed in the unofficial build.

Fixed in 2.0.99

Could there be a new function or monster seeking flag for projectiles?

Remove the NOBLOCKMAP flag from the shootable missile. That flag prevents any passive collision detection which includes being hit by another weapon.

The rest is just a result of doing something unsupported. To do this cleanly you'd have to program it in C++ to handle all the dependencies properly. I won't change A_CustomMissile because too many WADs already depend on the current behavior.

I'm experiencing some similar problems with my friendly weapon. I tried the friendly aiming thing by making something like the doom 3 bfg with the laser that shoots out at nearby enemies while the projectile is firing and making it so the projectile can be shot down without triggering the bfg wave. Unfortunately, the bfg shot cannot be shot down - attacks just go right through. The lasers also act strangely. They aim at nearby enemies, but they just pass right through them without harm. However, they can hit enemies that are further away from the projectile and happen to be in the path of the lasers. They also hit the player if the player happens to be in the path. I noticed that the lasers seem to be owned by the nearby monster that happens to be targeted by them. What I mean is that when the player is killed by a laser, the obituary displayed says that he was killed by the monster that the laser was supposed to be aiming at. Monsters have also started infighting as a result of the laser passing through the targeted enemy and striking the one behind it. This also explains why they pass through the targeted nearby monsters without harm. If there are no targets around, the lasers simply shoot at the player once the laser spawners are awakened.

[spoiler][code]
ACTOR BFGShot : BFGBall -1
{
Health 25 //1000
Radius 13
Height 8
Speed 5 // slowed down for testing purposes
Damage 100
PROJECTILE
+SHOOTABLE
+NOGRAVITY
+DROPOFF
+NOBLOCKMAP
+FRIENDLY
DONTHURTSHOOTER
SeeSound ""
DeathSound "weapons/bfgx"
States
{
Spawn:
BFS1 AB 4 bright A_CustomMissile("BFGLaserSpawner", 32, 0, 0, 2, 0)
Loop
Death:
BFE1 AB 8 bright

BFE1 C 0 bright A_JumpIfHealthLower(1, 2)
BFE1 C 8 bright A_BFGSpray
Goto Death+5

BFE1 C 8 bright
BFE1 DE 8 bright
Stop
}
}

ACTOR BFGLaserSpawner -1
{
Speed 0
Damage 0
PROJECTILE
MONSTER
+NOGRAVITY
+DROPOFF
+NOBLOCKMAP
+FRIENDLY
SeeSound ""
DeathSound ""
States
{
Spawn:
TNT1 AAAAA 1 bright A_Look
Stop // change to Loop for a nasty surprise!
See:
TNT1 A 0 bright A_JumpIfCloser(1024, 2)
TNT1 A 1 bright
Stop

TNT1 A 1 bright A_CustomMissile("BFGLaser", 0, 0, 0)
Stop
}
}

ACTOR BFGLaser : MageWandMissile -1
{
Damage 10
SeeSound ""
DeathSound ""
}[/code][/spoiler]

So Graf, any word now on why this latest method fires 2 projectiles and why one seeks you while the other seeks the closest enemy?

I just tried it and you're right it shoots two, and I can't figure out why.

	States
	{
		Spawn:
			TROO A 8
			Loop		
		Death:
			TROO B 1 A_Look
			Loop
		See:
			TROO B 0 A_CustomMissile ("ImpShot", 32, 0, 0, 0)
			TROO B 0 A_Fall
			TROO B 0 A_Scream
			TROO MOPQRSTU 2
			TROO U 2
			Goto Death + 11
	}

[code]
States
{
Spawn:
TROO A 8
Loop
Death:
TROO B 1 A_Look
Loop
See:
TROO B 0 A_CustomMissile ("ImpShot", 32, 0, 0, 0)
TROO B 0 A_Fall
TROO B 0 A_Scream
TROO MOPQRSTU 2
TROO U 2
Goto Death + 11
}
[/code]

Would this work? What were you trying to do with the loop at the last frame of the death sequence? If you were trying to make the corpse, just use a duration of -1 for the last frame. Your imp will probably just sit in place since it doesn't have a walking sequence defined and doesn't inherit one, so you could use the see state for the fireball.

EDIT: No it doesn't. The fireball just shoots right back at me. The fireballs shoot at the enemy if you put MONSTER in there. One fireball shoots at you while the other shoots at the enemy. Why two?

So is ZDoom capable of making htis or not? Is it possible to make a friendly enemy that when they are attacked by YOU they fire a shot at the nearest ENEMY and die?

Because A_Look jumps to the see state if it finds a target to attack. You are using the function in a place where it doesn't belong so you shouldn't be surprised that it doesn't work.

This still doesn't make any sense. Shouldn't a stationary friendly be just as simple to create as a moving one? Why is this so difficult?

[quote="Scuba Steve"]If A_Look is removed, then the monster no longer targets other enemies and only fires at the player.[/quote]


Then you have to define a valid see state somewhere (preferably directly after A_Look.) Without it it doesn't work.

I faced a problem like this a couple of days ago... my conclusion is that you can't use A_Look, or they will lose the +FRIENDLY flag. Just step straight to A_Chase.