So
#384 posted by madfox on 2020/03/12 04:03:40
Yes., it were the old bboxes. I think it's solved now.
2.32
Repositioning the saw gets queer in other than commen poses.
I think he catched a cold. :P
Why should we use poses that are not in the original game?
I could give the joker a spellmaster gig. It uses its arm to range, could be a backtrap spell.
#385 posted by yhe1 on 2020/03/12 04:32:54
You should make a version faithful to chasm first, then if you can get the spell attack working, then use that for a Joker boss.
#386 posted by yhe1 on 2020/03/12 04:42:52
The mong still ignores being hit at all. This is not a bbox problem. I think you need to restore an old version of the mong, maybe version 2.17
#387 posted by madfox on 2020/03/12 06:41:12
I only tested Faust and Goblin. They seemed to have good infight.
What Mong concerns I can't get grip on its behaviour.
When all have left fighting it is the only one left behind.
Can't make a thing of it. Needs a kick-ass.
With file 2.17 all attacks were scrambled with hitscans by ai_charge.
I had to start over again.
#388 posted by yhe1 on 2020/03/12 06:54:08
Then use 2.16 or earlier, the mong's infight work fine back then
Mong
#389 posted by madfox on 2020/03/12 23:19:28
- Returned Montgrunt v2.13. Infight is better now.
- Joker with fist repositioned handsaw. first stage.
2.33
#390 posted by yhe1 on 2020/03/13 04:50:11
There seems to be no change in Mong behavior. Check if a mong will fight with a enforcer, and check if a stratos will fight with an enforcer.
#391 posted by yhe1 on 2020/03/13 22:59:43
Can you give sacrof armblade to joker?
Ah,
#392 posted by madfox on 2020/03/14 01:42:30
Given a chasm/quake.mdl is strictly bound to vert/tris count and skin seize.
I can create a new skin, change the pattern within the mdl file, but that's about all.
It's possible to merge an object into the excisting one by cost of doubling the skinseize. (original + import = 2). Shrink the merging object as small as possible, but still the whole skin file will be lashed.
I've studied the error with Mong, and something strange come to me. MonGrunt has the exact the same code as the Enforcer, with altered launch function aside, but in game they won't hardly have infight.
If I take two Enforcers, they won't attack eachother either, so I think that is what's happening. Code wise it are identicall monsters, so they won't have infight.
The last string I could find is in:
void(vector org, vector vec) GrunLaunchLaser =
{
if (self.classname == "monster_grunt")
If Enforcer has the monster_enforcer code here they will have infight. What happens is that Mong will give an attack, but then quickly starts hunting again. Unfair, as its health of 180 fails enforcer's 80.
#393 posted by yhe1 on 2020/03/14 06:20:24
Madfox, not sure if you understand me 100%, but the joker's handsaw is a like a skin. The only limitation is that the edges must be straight. well, the scarof's sawblade can be straight edged and not look bad. maybe you can try to make a Scarof blade with the skin file, then shrink it and attach to joker's arm.
Regarding Mong infighting, what if you replaced both the mong and the stratos with the version right after the boundbox bug was fixed? I remember mong and stratos infight worked fine back then.
#394 posted by madfox on 2020/03/15 01:58:53
dev2.15 is the last where mong has a kind of infight.
Bad is that it isn't that easy to copy all files back, because all errors with stale frames are back again.
There is no difference in the mongrunt.qc or fight.qc so it stays a wonder to me.
No
#395 posted by madfox on 2020/03/15 23:22:56
I've gone back to dev2.09 and although in that map mong seems to infight, as soon as I use the dev2.09.qc and try it on a map there are only mongs that react with a counter attack, but then run blind to the player.
I get a bit irry about this stupid error.
I wanted to make chasm monsters work in quake,
not why they won't fight eachother.
You Shall Not Chasm In Quake
#396 posted by madfox on 2020/03/17 03:40:34
A bit hillarius about the mong accident. I think it's there but it is a small error compared to the things that work well. :P
Anyway, this is as far as I have come and I know there are attack scenes that could do better. But I'm no coder, as good as I can do.
Here's is the latest map, I didn't change much. I deleted the Grunt_check_Attack in fight.qc after I saw it make ingame fights. But they are much to obvious. Not ment as a truely counter attack.
dev2.34
#397 posted by yhe1 on 2020/03/17 04:16:12
what about using Quake Grunt code instead of enforcer code for the Mong?
#398 posted by yhe1 on 2020/03/17 05:55:23
How come the mong fires a little arrow now instead of the correct attack (shotgun)?
#399 posted by madfox on 2020/03/17 08:20:07
I've been trying different attacks for mongrunt to see if it changes the infight.
The original code was the quake grunt, but soldiers don't infight eachother.
The small arrow is the frame of the animation becausw I switched the code to enforcer.
Not enough to make it more alert, which is strange because the other chasm monsters with quiete the same code have no trouble with infight.
#400 posted by yhe1 on 2020/03/17 08:43:15
what code is the alien warrior based on? The alien warrior is one monster that never had any problems with infighting. maybe use alien warrior code for Mong?
Infight
#401 posted by madfox on 2020/03/18 02:40:57
Most chasm monsters are made up by altered enforcer.qc.
The little arrow is the goblin code used for the mgrunt.qc.
The longer I change the attack code for mgrunt, the more I come to see that this isn't the cause of the error.
All other chasm react the way they should do with enforcer code.
Only Mong seems to be the exception that won't relate to the infight code.
If it would be the soldier/grunt attack it would be clear as they don't infight eachother.
But whatever attack code I give to Mong, after one or two counteracts he just stops, as hunting player_target is prior.
I see no reason why target = self.enemy; only leads to player attack, and not on other monsters.
#402 posted by yhe1 on 2020/03/18 03:34:20
Perhaps IW or qmaster can step in and fix this infight error again lol
#403 posted by yhe1 on 2020/03/18 03:50:42
look at the code of the AD shotgun enforcer?
#404 posted by madfox on 2020/03/19 00:12:39
I changed all references to grunt into mong to assure there is no relation with grunt or army whatever.
The only way to get the buck go infight is to delete its melee attack bite, then 25% change it goes infight.
Let's call him JackPotMong!
#405 posted by yhe1 on 2020/03/19 04:42:00
what bite attack? Mong only has punch and kick melee attack
Yes
#406 posted by madfox on 2020/03/19 19:25:24
But they are ordered with an altered dog bite attack which is split up in punch & kick.
#407 posted by yhe1 on 2020/03/19 19:47:00
so the mong no longer punch and kick?
Not So Fast
#408 posted by madfox on 2020/03/19 20:56:00
I'm just testing why the mong won't infight. Deleting as much attack statements may show why it won't leave the player alone and concentrate on other enemies.
Mong has two attack scenes, bite that is used for push and kick and the shoot scene.
Placing an army and mong in a map the infight always goes one way. Mong gets shots, fires one or two counter attacks and if the army soldier would not interact it wouldn't fight back at all.
So deleting the bite attack would make it only survive in the shoot attack. In that case it would have the exact code as the army guy. And they should fight eachother.
Just don't get it why mong is so concentrated on the player, leaving other enemies out hand.
|