Forum

Questions about entity exclusion bitflags on mapload

Discuss programming in the QuakeC language.

Moderator: InsideQC Admins

Questions about entity exclusion bitflags on mapload

Postby Dr. Shadowborg » Fri Jan 01, 2010 12:01 am

Okay, starting out what I'm doing now is working on adding deathmatch support to my SP map, and I want to add a deathmatch only flag to stuff like trigger_teleport, func_wall, etc.

Are the "not on skill x / Deathmatch" bitflag exclusions hardcoded into the engine?

Also, does nightmare break this? i.e. If I set a trigger entity / func_wall to not be on easy, normal and hard, will it appear on nightmare?
User avatar
Dr. Shadowborg
InsideQC Staff
 
Posts: 1110
Joined: Sat Oct 16, 2004 3:34 pm

Postby FrikaC » Fri Jan 01, 2010 12:14 am

Yes the exclusions are handled engine side. ('Hardcoded' is such a funny word in a open source engine). Nightmare uses the "hard" bitflag for spawn exclusion.
FrikaC
Site Admin
 
Posts: 1026
Joined: Fri Oct 08, 2004 11:19 pm

Postby Dr. Shadowborg » Fri Jan 01, 2010 12:34 am

FrikaC wrote:Yes the exclusions are handled engine side. ('Hardcoded' is such a funny word in a open source engine). Nightmare uses the "hard" bitflag for spawn exclusion.


Ah, cool then that just means I have to configure quake.fgd to actually use the "not on X" flags.

Hardcoded in this case is slightly lame, but I'll work around it.

Thanks for the reply and have a good New Years Eve / Day Frik! :D
User avatar
Dr. Shadowborg
InsideQC Staff
 
Posts: 1110
Joined: Sat Oct 16, 2004 3:34 pm


Return to QuakeC Programming

Who is online

Users browsing this forum: No registered users and 1 guest