A_ItemSpawn() Problem

[Zajo]

Why does this not spawn an imp in front of the warlock?

Code: Select all

actor Warlock : Archvile 30001
{
	speed 12
	painchance 40
	
	states
	{
		Missile:
			VILE G 0 bright A_VileStart
			VILE G 10 bright A_FaceTarget
			VILE H 8 bright A_SpawnItem("DoomImp", 0, 0, 1, 0)
			VILE IJKLMN 8 bright A_FaceTarget
			VILE O 8 bright
			VILE P 20 bright
			goto See
	}
}

[bagheadspidey]

I'm not sure about this, but maybe try spawning it a little farther away?

[Zajo]

That helps a bit, but the documentation says that 0 means to spawn the thing the closest possible to the calling actor. Also, I need just that to happen, because I plan the warlock to spawn several types of monster, not just imp, and I would have to set the distance manually for every type. Is the function corrupt?

[Matt]

A_SpawnItem only spawns if there's enough space for the object. Problem is, the check is a bit finicky and tends to err in favour of not spawning.
[wiki]A_SpawnItemEx[/wiki] lets you skip the space check, among other things. Don't be surprised if you get monsters stuck in walls or other solid actors, though...

[Zajo]

That's why I'd never use such a function, or better said, the option to skip the check.

[Unknown_Assassin]

The best way I can think of this is to make the Archvile make a projectile and uses A_CustomMissile. That projectile can then spawn a monster.

If you want an example, check the Imp Warlord in the Monster Resource Wad

MRW

[Matt]

The projectile stores its owner as a hate target, so the spawned monster will either attack the warlock or (if it can't target the warlock) stand there until it sees a player.

[Unknown_Assassin]

The projectile stores its owner as a hate target, so the spawned monster will either attack the warlock or (if it can't target the warlock) stand there until it sees a player.

I just test it. The Bat Familiar and Dragon Familiar that were spawned didn't hurt the Imp Warlord.

[Matt]

I just test it. The Bat Familiar and Dragon Familiar that were spawned didn't hurt the Imp Warlord.

It custommissiles a dummy actor that then custommissiles the familiar. Try it with the monster targeting another monster, or move so that the familiar doesn't spawn facing you - that's the problem I'm thinking about.

As well, the custommissile always spawns the actor (i.e., it never does the A_SpawnItem check); the spawned actor just dies instantly if it's stuck.

[TheDarkArchon]

I just test it. The Bat Familiar and Dragon Familiar that were spawned didn't hurt the Imp Warlord.

It custommissiles a dummy actor that then custommissiles the familiar. Try it with the monster targeting another monster, or move so that the familiar doesn't spawn facing you - that's the problem I'm thinking about.

As well, the custommissile always spawns the actor (i.e., it never does the A_SpawnItem check); the spawned actor just dies instantly if it's stuck.

A note on this: If you do decide to do this, then you need to have the first death state have A_Die to handle failed spawns properly.

[Unknown_Assassin]

Try it with the monster targeting another monster, or move so that the familiar doesn't spawn facing you - that's the problem I'm thinking about.

Whoops. The Imp Warlord was a bad example. I was actually thinking of the DESentinel. It uses A_CustomMissile.