non-solid func_bob becomes solid when you walk over a corpse 

I have a monster_ogre, and when I add a key value pair of
ammo_shells: 20
I gain 20 shells when I kill him and touch the dropped backpack.

This does not work with ammo_rockets however, because in ogre.qc it sets self.ammo_rockets = 2. Is there a way so it respects my values in the entity settings? 

Hey everyone,

I'm a newbie working on mapping with Quake 2 in Trenchbroom (loving the editor so far!)

Unfortunately I can't seem to generate a map with proper lighting due to a leak while running QBSP3.

I can still launch the map, however after compiling with QVIS3 it will be dark.

In order to troubleshoot I started a new file which is a simple closed off room, ensured my "Snap to Grid" option is on, and that the room is indeed closed off.

Here's what the compiler is doing:

#### Executing 'E:\Games\quake2\baseq2\qbsp3.exe q24'
----------- qbsp3 -----------
original code by id Software
Modified by Geoffrey DeWan
Revision 1.09
-----------------------------
gamedir set to E:\Games\quake2\baseq2\
entering E:\Games\quake2\baseq2\maps\q24.map
0...2...5...7... (0)
**** leaked ****
Writing E:\Games\quake2\baseq2\maps\q24.bsp
0 seconds elapsed
#### Finished with exit status 0

#### Executing 'E:\Games\quake2\baseq2\qvis3.exe q24'
----------- qvis3 -----------
original code by id Software
Modified by Geoffrey DeWan
Revision 1.03
-----------------------------
reading E:\Games\quake2\baseq2\maps\q24.bsp
reading E:\Games\quake2\baseq2\maps\q24.prt

************ ERROR ************
LoadPortals: couldn't read E:\Games\quake2\baseq2\maps\q24.prt

#### Finished with exit status 1

#### Executing 'E:\Games\quake2\baseq2\qrad3.exe q24'
----------- qrad3 ----------
original code by id Software
Modified by Geoffrey DeWan
Revision 1.04
Compiled for Pentium processors
-----------------------------
gamedir set to E:\Games\quake2\baseq2\
reading E:\Games\quake2\baseq2\maps\q24.bsp
Couldn't load E:\Games\quake2\baseq2\textures/__tb_empty.wal
No vis information, direct lighting only.
0...1...2...3...4...5...6...7...8...9... (0)
0...1...2...3...4...5...6...7...8...9... (0)
writing E:\Games\quake2\baseq2\maps\q24.bsp
0 seconds elapsed
#### Finished with exit status 0

Here's the map:

https://drive.google.com/open?id=1Aewjw4W7CVy729usfuW757d1DemlUbZp


Any help would be greatly appreciated! 

Have you tried 'File > Load Point File'? It should tell you where the leak is.
Have you tried different textures? The compiler complaining about __tb_empty means you have untextured brushes. Not all textures seal against the void.

I can see that the geometry shouldn't be leaking, but I don't have Q2 or its compilers installed. 

Hi nathnolt. Afraid that can't be done without modifying the QC. Map hacks involve getting interesting effects from setting values in fields which the QC has assumed are set to default. If the QC explicitly changes a field, you can't tell it not to do that.

Sometimes you can work around things the QC does, either by:
- using a hack earlier on to prevent the offending QC running
or
- running another hack after the offending QC to overwrite the value
Neither of these work for the ogre ammo, because the ammo value is set in the same function which drops the backpack. If you found a way to skip that, you'd skip the backpack spawning as well. If you rewrote the ammo value later (which might not be possible anyway...) you've missed the change for it to count. 

Thanks @Preach, both for your reply and your website. Is there a list with the combined knowledge of map hacks and/or entity knowledge? 

Hi.
Now that I'm getting closer to finish alpha-stage of my map, I'm wondering if I could implement the trigger_cdtrack from Arcan Dimensions to my progs_dump.
I have the fteqcc but absolutly no idear where to start.
Is there someone into QC who can tell me how to do this?

best wishes 

It's pretty involved. AD is a near re-write of the QuakeC logic so lifting anything from AD is a pretty advanced IMO.

That said I have not looked at that code so maybe it's a straight port?

QuakeWiki Modding Tutorial:
https://quakewiki.org/wiki/Getting_Started_Modding

QuakeC tutorial:
http://www.insideqc.com/qctut/

QuakeC Reference Manual in PDF:
http://pages.cs.wisc.edu/~jeremyp/quake/quakec/quakec.pdf

QuakeC Manual website version (with nice text formating):
http://www.cataboligne.org/extra/qcmanual.html

FTEQCC compiler:
http://fte.triptohell.info/moodles/fteqcc/

FTEQCC documentation:
http://icculus.org/~marco/quakec/fteqcc_manual.txt

Progs v1.01 source code:
https://github.com/id-Software/Quake-Tools/tree/master/qcc/v101qc

Progs v1.01 source code: (cleaned):
https://gitlab.com/quakec-v1-01-clean/quakec-v1-01-clean/commits/master

Progs v1.06 source code:
http://www.moddb.com/games/quake/downloads/quake-c-version-106

Hipnotic SDK:
http://www.gamers.org/pub/idgames2/more_idstuff/hipnotic/ 

Wow! Thanks!

A lot to read.

Thought of a free weekend. Haha :)

best wishes 

I will take a look at this qc for you as well but no promises on any real code unless it's something simple! 

Hi nathnolt, bit of self promotion but you could start with the map hacks posts on my blog. The earlier ones tend to be the simpler ones...

https://tomeofpreach.wordpress.com/category/map-hacks/ 

@ZungryWare has compiled an exhaustive list of hacks here:

https://scalar.vector.im/etherpad/p/r.6ad54765f5b9b714d4501dbb1b728c7f 

Thanks everyone for the help & support. 

also if you haven't seen it yet, there is a whole long-running thread about map hacks:

Teaching Old Progs.dat New Tricks 

I think I've found all necessary functions in the progs and definitions.
I will try to copy and paste after the weekend and tell if it works. 

I tried and failed.
Seems I've got to read more into detail. 

I will take a look this evening. (I said that before but forgot.)

I will report back here. Adding a reminder on my phone for after work. 

I was able to get a CD track to play using the built-in command SVC_CDTRACK

I have a killable Chthon and added this to the end of the function where he gibs.

WriteByte (MSG_ALL, SVC_CDTRACK);
WriteByte (MSG_ALL, 3);
WriteByte (MSG_ALL, 3);

Track 3 played perfectly from my music directory.

You need to repeat the 2nd command for it to work. In Quakespasm I got developer errors about not finding the CD track but that is only in dev mode and the music still plays. If you need further help I would need to see what you are coding.

As far as using the AD functions, that's a bit too much work for me and I am not sure I could get it to work properly. Try the built-in id function first. 

Thank a lot!

i was able to find the code for cdtrack in the targets.qc and built it in the progs.dat but finaly struggled, from my point of view, with the definition of the functions.

I*m looking forward to check the SVC_cdtrack this week and tell you if it works.

best wishes. 

WriteByte (MSG_ALL, SVC_CDTRACK);
WriteByte (MSG_ALL, 3);
WriteByte (MSG_ALL, 3);

Track 3 played perfectly from my music directory.

You need to repeat the 2nd command for it to work.

The second writebyte is setting a variable called cl.looptrack - which on first glance you would expect would control whether the track loops or not. Surprise! It's not actually implemented in the engine, so the track always loops. You are free to send any number in the second WriteByte, it doesn't need to be the same as the track number.

If you'd like to play a CD track without it looping, the alternative is to use stuffcmd with the console command "cd play 3". You can also replicate the looping cd track from the SVC_ command with "cd loop 3". 

Ok, I thought the whole thing over and came to the conclusion that whatever I will do, I have to make it a trigger_cdtrack. Otherwise it will not work with the mod.
That means getting into the whole qc-thing and read a lot.
So at this point I will finish mapping first before doing anything else.
Thanks to dumptruck_ds and preach for the assistance!
Hope I can ask you again when the job is done.

best wishes 

One last thought: If the mod you're using has the equivalent of
trigger_command then you can use the console command to achieve what you're after without modifying it.