.qc (dot qc) - the group for quake c coders of all denominations. If you make quake one mods and write code in quake c, join our group! I'll try to answer any quake c questions - please post your inquiry in the forums...

  • View media
  • View media
  • View media
  • View media
  • View media
  • View media
Sticky
embed
share
view previous next
Share Image
Share on Facebook Post Email a friend
Embed Image
Post comment Comments
numbersix Author
numbersix - - 2,244 comments

One of my qc bits - spikes sometimes get stuck in walls
I call this the "Robinhood" effect...
I havent tried sticking them in living stuff yet, but that is an idea
I'll have to put this bit in the vault

\|/
-Number Six: Patreon.com
/|\

Reply Good karma+1 vote
ceriux
ceriux - - 1,514 comments

I tried once but getting them to follow is a pain.

Reply Good karma Bad karma+2 votes
numbersix Author
numbersix - - 2,244 comments

Yeah, its a toss up between:

#define MOVETYPE_FOLLOW 12
//description:
//MOVETYPE_FOLLOW implemented, this uses existing entity fields in unusual ways:
//aiment - the entity this is attached to.

and ...

void(entity e, entity tagentity, string tagname) setattachment = #443; // attachs e to a tag on tagentity (note: use "" to attach to entity origin/angles instead of a tag)

I use attachment for viswep and it works pretty well.
But both of those can be a bit quirky.

With attachment I believe the nail will stay where it stopped.
Just have to add some attachment manage code in the think that removes the nail.

The main thing is that where they stop on a monster model or what have you is not necessarily visually ideal.

Reply Good karma+1 vote
Post a comment

Your comment will be anonymous unless you join the community. Or sign in with your social account:

Description

spikes done different