InsideQC Forums

This wouldn't help, because the external visible weapon models match the player's angles, not v_angle.

But hey, this issue is "partially" fixed.
If you run a DP server and connect with a DP or FTE client this won't happen, but if you run a DP server and connect with a regular engine this will ...

It uses DP_CHECKEXTENSIONS.
You can run it on practically any engine, except regular WinQuake (you'll get skin taller than 300 errors), but WQPro will run fine.

If you run it on DarkPlaces or FTE, the only thing that changes is visible weapons support, just set 'temp1' to 1.

OK I finally decided to update this.
There are now 18 waypointed maps in total, and that visible weapon bug was fixed. It's now handled by 'temp1' cvar.
Also detpacks will now destroy walls, grates etc.

File (10mb):
http://www.quaketastic.com/upload/files ... _beta2.zip

Look for ai_melee() and ai_melee_side() in fight.qc, change that 'ldmg' value.
Note that this will also change the death knight's sword damage.

Unfortunately Quake only uses ONE bounding box per entity. On modern games there are multiple bounding boxes for each part of the body, or per-poly collision. So locational damage gets a bit weird in Quake because of that but anyway I still like it.

See a simple diagram below:

http://img826 ...

Lardarse is kinda right. Setting .owner to .enemy, will make the monster non-solid to the player (if the player is the monster's enemy, otherwise this monster would be non-solid to another monster). So the monster will ONLY take damage from explosives. Hitscan and projectile/grenade weapons will ...

Like Spirit said, there's no way to load 2 mods at the same time.
But in a simpler way, you'll need to find nehahra source code, rogue source code, and put the rogue monsters .qc files into the nehahra source code, modify progs.src properly and then compile.

I'd call it 'Normal Quake'. Some years ago, I though NQ was for 'Normal Quake', not 'NetQuake'.

Actually I didn't made the code, I taken it from TF source code and adapted it to my mod.


void() CheckSpeedHack =
{
local float tf, pf;
local vector vplf, vf, ang;

self.nextthink = time + 2;

if (self.owner.deadflag)
return;

if (!(self.owner.flags & FL_ONGROUND) || self.velocity_z != 0 ...

If you want to prevent QW-style acceleration in zquake/mvdsv/fte just set pm_bunnyspeedcap 1
Same physics, no bunnyhop acceleration.
Note that you can still propel yourself quickly using rockets, but you'll slow down again if you turn... At least I think you will.

OMG! *facepalm*
The mod is NQ ...

Try -listen 16 on the command line.
Then set deathmatch to a value other than zero, teamplay to 1 or 2, and maxplayers to 16. On NQ the command is maxplayers, not maxclients.

@scar3crow This also happened to me. Often. Mainly if I'm a Scout.
At that time I didn't figure out how to fix that, but I realized that I just needed to change some numbers on the cheat checking function. That function is to prevent players changing their cl_forwardspeed and so to values higher ...

The only real complaints I have with this is that the revolver is ugly (not your fault though) and that the bots are a bit too reaperbot like with their aim.

Agreed. When I converted the revolver model to Quake, I had to unify its textures to a bigger image file, and then set the texture ...

I'm seriously thinking on doing it, and it's not hard.
Maybe I'll release this as a little patch...

Don't forget to set teamplay to 1 (teamkill off) or 2 (teamkill on). :wink:
If you set to zero the bots will pick random colors, and they won't have any team_no assigned, that's why they'll spawn on info_player_start instead.
And UrbanKid, it runs fine on any engine. But if you run it on dp or fte ...