It's easy to make typos on these tiny virtual keyboards. Since tell and yell are both valid words, Android proposes them both to choose from above the keyboard. If you forget to pick one, it's not Android's fault... ;)

Sorry for the OT, guys. 

My phone is large enough that the keyboard is actually very reasonably sized for thumb use. I decided to just turn off autocorrect completely anyway, if I really need it the suggestions bar is still there...

In OTish news, what do people think about hiding small items in total darkness? Right now there's a rotten health hidden in a little alcove that's pretty easy to spot but unlit. Should I throw a little light in there or is it okay to have something you'll only really find by accident like that? 

Many engines support it, and it's no different from bsp29 other than increased limits on just about everything. Nobody will be mad at you :) 

hiding small items in total darkness
That's a no-go in my book, unless it counts as a secret - but a secret for just a rotten health might be a bit of an overkill.

That said, wouldn't the fullbright parts of the health box make it noticeable?

Didn't know you could still use the suggestions bar with autocorrect off. 

Suggestions bar depends on your keyboard. I use Google's "GBoard" on my phone.

And there are no fullbrights on the health pickups in AD's medieval set.

I think you're right about it being a no-go. The fact that I wasn't sure about it should have told me all I needed to know about the placement... 

Does anyone have advice on how to build something like this out of brushes? I want to make it hollow on the inside as well.

Thanks! 

Round and hollow? example 

Duke of Ontranto

https://www.quaddicted.com/reviews/fc1.html

In pak, see ---> progs/barrel.mdl

Live action -game fc1 +map fc1m2 

In JACK, create cylinders stacked, in vertex mode use CTRL+E (or maybe it was ALT+E), scale edges as needed. It helps to have both mating brushes selected...this works for donuts as well as cylinders. 

I don't remember reviewing fc1... It's been a while since I played through any maps in quake actually.

Those barrels are decent, actually. I ended up figuring out how to make them out of brushes by looking at the wireframe in qme. 

I use TB2, but I was able to achieve a (probably) similar effect with the basic vertex manipulation there. :)

Now i just have to cut my beautiful new barrel up into little chunks so it looks cool when you shoot it to bits! 

I'm not sure if you know this but a protip i recently found from Sleepwalker was: You can use CSG Merge to merge faces in Tb2! Make the diff sections of your geo then use merge to quickly extrude the brushes. Try it.

Also there are barrels in Hexen 2 that could probably be used as a template. I wonder if the map source is available? 

Hey, I loaded up the AD .fgd file and made a symlink of the "progs" folder into Trenchbroom's root directory assuming it would be able to find the models there, but it seems that it can't, where do I need to place it so that Trenchbroom will find them? 

You don't need to symlink anything. Just make sure that TB knows where your Quake directory is and select the mod's folder here!

There are essentially two places where you need to set up your mods (at minimum): Under the map tab, where you select the mod folder, and under the Entities tab, where you select your entity definition file such as a .fgd or a .def

Hope that helps :) 

If I wanted to take away a players weapons after the end of a map, like what happens at the end of each episode in quake, what's the best way to do that?

Also is there a way to change the name of the start map that is automatically loaded when quake starts, or does it always have to be called "START" ? 

best way to do that is to give the player a rune and use the info_player_start2 entity

also I'm pretty sure that you can set the start map in the autoexec.cfg... not certain though. 

"map start" is hardcoded in the engine for when you start a new game through the menu 

Preach might remember better but I believe a trigger hack with negative items might do the trick to act as a weaponstrip.

info_notnull:
think InitTrigger
nextthink 0.2
touch weapon_touch
items -2048 (add weapon numbers here) 

Actually I don't think that would work, not sure how bitwise | treats negatives. 

Hmm interesting, thanks guys. We will probably use the rune method unless we can work out a hack (this is for QUMP) 

Try looking at DecodeLevelParms in client.qc. This is entirely a QC controlled thing, you don't need a hack. 

some engines (ie: fte+dp+qss) have startmap_sp and startmap_dm aliases, which can be set eg:
alias startmap_sp "map foo"
which should normally be done in your mod's default.cfg file.

the engine then goes and executes those aliases instead of directly loading the regular start map.
an alias instead of a cvar allows you to reset various other cvars before the map loads (or plays a demo/intro first or whatever).

as far as the engine is concerned, map start isn't otherwise special.

as far as the vanilla qc is concerned, players will always spawn with default weapons on start.bsp, the qc prevents any weapons from other maps from being restored on the new map.
It should be relatively simple to create a trigger to remove items, but it'll still need custom QC.

If you're looking for a hack to remove the player's weapons+ammo+armour without using start.bsp and without custom QC, you might be able to achieve that by killing the player with an insta-gib trigger_hurt overlapping a trigger_changelevel. Both triggers need to be touched within the same touchlinks call - otherwise the player will become non-solid and be unable to trigger the other trigger (teleporting the player into a room containing both triggers should do it reliably enough).
(obviously this requires a map change) 

I need a reminder here.
corps_removal added to the death_frames, and an update to defs.qc.

I forgot how, anyone who can light up my little light? 

You could create a body_fade function and adjust the alpha.

body_fade = {
self.alpha = self.alpha - 0.1;
if (self.alpha < 0.1) {SUB_Remove (self); return; }
self.think = body_fade;
self.nextthink =time + 1.00;
};

Then in the death function of a monster you could add something like this:

void() madfox_die8 = [89, madfox_die8] {
// Fade slowly
if (cvar("fade_corpse") == TRUE) {
self.think = body_fade;
self.nextthink = time + 0.1;
} else {
// Just remove after 30s
if (cvar("fade_corpse") == 2) {
self.think = SUB_Remove (self);
self.nextthink = time + 30;
}
}
}; 

Thanks for your guesture, qmaster.

After digging deep this came up:

Add to defs.qc
void () CorpseThink =
{
self.think = SUB_Remove;
self.nextthink = time + 30 + random() * 30;
};

All death frames monsters

void() sham_death11 =[ $death11, CorpseThink ] {};

I knew it was something simple.
Thanks anyway.