, well unexpected due to my lack of knowledge anyway, with my new quake project.I've posted over at Inside3d.com, as they more often than not will know the answer, but I thought that asking here as well would be useful
Anyway here's the problem:
I'm trying to get a particular monster (e.g. ogre) to walk through walls and through the player, I've tried adding the following;
self.solid = SOLID_NOT;
self.movetype = MOVETYPE_NOCLIP;
in ogre.qc, which has acheived my first aim of the player being able to walk through it and shoot through it, but it still turns away from the player and won't follow a path thru' a wall.
It already otherwise "ignores" the player (as in doesn't react to, either when attacked or when the player comes in view) , thru ammendemnets to float() FindTarget in ai.qc, but there still appears to be a recognition of the player elsewhere. Also, although theoretically the movetype_noclip should allow it to pass through a wall, it turns before doing so.
I'm kind of concerned that the code for stopping monsters from touching walls or the player is in the engine rather than quakec, which, of course, would fairly bork this idea in terms of a DcQuake mod.
In terms of priorities, it's more important to me to get it walking through walls, than it is for it to "agree" to walk through the player.
Any pointers/ideas?
cheers
ajay
but I'm getting there....
