Is http://home.kpn.nl/lo2kf8/quake/Q1test_src.zip a decompile of the original, or is this self-made attempt to recreate after the fact? Wow! Which version of FTE did you use to make the decompile work?

You are a true saint!

I examined the progs.dat in a hex editor, and it appears to have entries for the monsters. So it seemed we could reverse it an peer back into time. 

Quaketastic can give you more info about the content and purpose of Q1test. There was never an official release of the Q1testQcc.

The breakpoint is that a compiler can't find the starting progs.scr. So it stops at that point. I recollected the bits after looking at the animation frames and comparing with the original code.

As the readme says it was only a try out to see if the internet connections were OK. So the added Sp monsters are lame as used for DM, aside they were included.

My idea was to add the monsterplay for Sp, add a qc for the Serpent, Vormit and ClassicOgre and make it compatible with the other monsters in SP. The result is Q1Test_SP. I would apreciate if you take a look at it.

Megalol also did a start with a convertion for it some years ago. 

Thank you for both the explanation and the attention to detail you paid in recreating/restoring this. I am really impressed with your work.

I am familiar with original QTest from the '90s and my childhood. Mostly what I was interested in was trying to ascertain a deeper understanding of what the actual single player game might have looked like from a https://tcrf.net/Proto:Quake_(PC)/Qtest1 perspective. The history and intent is really the past I am fascinated about. I recall (it's years) the original "Quake 2" comment stubs in the original QuakeC. These felt nuts in retrospect to see, "guys, you're not even done with the first game; what are you thinking?"

I was thinking about doing something to the effect of a unified diff https://en.wikipedia.org/wiki/Diff of the extracted QuakeC from QTest versus the QuakeC from the original v1.01 dump. Of course a fair bit of noise would exist due to code reflowing and comments. I don't suppose anyone ever made a automatic formatter for QuakeC á la https://blog.golang.org/gofmt? ;) 

4LT posted this in discord:

Well, the grenade fix seems to be working as it should now. You can patch it into your mod now, you just need to add this file to your project, patch GrenadeTouch and OgreGrenadeTouch to call GrenadeHandlePhysics (don't forget forward declarations!), and be sure to check the source to make sure we're not trampling eachother's entity fields.

https://github.com/4LT/qc-necrotelecomnicon/blob/master/grenade_fix.qc 

Forgot to mention, you'll also need to snag the "reflect" function from math.qc

But, you'd figure that out soon enough I suppose. 

How can i use waterjump end of the ladder 

I want to make a Quake mod, and I just need to change a few simple things but I'm having major trouble finding any info on how this is done

I want to make a texture wad, I want to change the player's speed in game, so that when people play my map's they don't have to go into the console and slow the player down themselves, and I want to edit weapons, mainly the axe and shotgun, any good guides I should find? 

For making texture wads I should use progs like Texmex or Wally. Changing a player's movements are more like a qc matter. It are two different archivements. One is mapping, the other is code modding

You can find a lot of info on quakewiki. But as I think it takes some time to make the workaround your own. 

LB79, you can change the player's speed in your mod by just adding cl_forwardspeed [value] and cl_sidespeed [value] commands in an autoexec.cfg or quake.rc file. 

THe thing that stands out to me is this line:

parm9 = self.armortype = 0.3; //this is the green armor type

First, you should not be assigning to self.armortype here, just assign to parm9.

Second, armortype parms need to be multiplied by 100 when stored to parms, so you should do

parm9 = 30;

(they get divided by 100 in DecodeLevelParms)

Try that and see if it helps. 

Thank you again!!! I'll try this! :) 

It's me again!

The "parm9 = 30;" works like a charm :)

You're awesome! 

I am trying to make a kind of countdown timer display for powerups in CSQC (for Quakespasm-Spiked). The idea is to have five transparent overlay images for the powerup icons (Quad, Ring of Shadows etc) which cover more and more of the icon when a powerup moves towards expiration.

One of the many things I tried:

if (autocvar(cl_pwrtime, 1) == 1)
PowerupTimer();

I added this function above it:

static void PowerupTimer()
{
entity ptimer = spawn();
ptimer.nextthink = time + 5;
ptimer.think = PowerGFX1;
ptimer.nextthink = time + 5;
ptimer.think = PowerGFX2;
ptimer.nextthink = time + 5;
ptimer.think = PowerGFX3;
ptimer.nextthink = time + 5;
ptimer.think = PowerGFX4;
ptimer.nextthink = time + 5;
ptimer.think = PowerGFX5;
remove(self);
};

And before that (I am not listing all functions, just the first, and only for one powerup):

static void PowerGFX1()
{
if (sitems & IT_QUAD)
drawpic(pos+'272 8 0', "gfx/sba1_quad", '16 16 0', '1 1 1', 0.5, 0);
};

There are two problems here:
- The replacement image doesn't show up ingame. Tried with text (drawstring) and it also won't work.
- I don't know how to port over the vector "pos" (it's used in the function that draws the itembar on top of the statusbar). 

I don't know anything about QCSC, but my default assumption is you'd need to call drawpic every frame, rather than the pic staying on screen until the next time you call drawpic with a different image. Second, can entities call drawpic? A quick google search makes it seem like you have to draw all images from within Hud_Draw. 

Yeah, seems it's possible you can't draw images with entities. What about reading the powerup timer and switching the image instead of taking a break, then? Something like this in the item bar drawing function, right after powerup icons are drawn:

if ((sitems <= 25) && (sitems > 20)) drawpic(pos+ppos, "gfx/sba1_quad", '16 16 0', '1 1 1', 0.7, 0);
else if ((sitems <= 20) && (sitems > 15)) drawpic(pos+ppos, "gfx/sba2_quad", '16 16 0', '1 1 1', 0.7, 0);
else if ((sitems <= 15) && (sitems > 10)) drawpic(pos+ppos, "gfx/sba3_quad", '16 16 0', '1 1 1', 0.7, 0);
else if ((sitems <= 10) && (sitems > 5)) drawpic(pos+ppos, "gfx/sba4_quad", '16 16 0', '1 1 1', 0.7, 0);
else if (sitems <= 5) drawpic(pos+ppos, "gfx/sba5_quad", '16 16 0', '1 1 1', 0.7, 0);

(This doesn't work right now, ofc.) 

2d drawing requires specific ordering.
draw it before the renderscene() call and it'll just get drawn over. draw it before the sbar's background and it'll still be covered up by said sbar.

doing it inside an entity's think function will draw it one frame in a thousand... AND behind the 3d view so you'll never see it anyway. trying to do it inside a touch function is pure insanity.

even making your own .draw event and manually looping through all entities via nextent will mean that respective ordering will not be well-defined.
you may wish to use linked lists instead - ones you can control the order of.
Or just insert extra conditions into the relevant places, with any timers using globals or statics (besides, doing it each frame means you can get smooth colour/alpha changes instead of abrupt). 

Unfortunately, my CSQC knowledge is kinda limited. If I wanted to have these timers using globals, what would that have to look like?

I basically need two timers, one lasting 30 secs (with stuff to do after 5, 10, 15, 20 and 25 secs) and another one 45 secs (same with 7.5 sec intervals), starting count for each of the powerups available in Quake, SoA and DoE. 

It seems to work with this code:

static float poweruptime;

[...]

static void PowerupTimer(vector ppos)
{
poweruptime = (time - 5)*10;
if ((poweruptime >= 200) && (poweruptime < 250)) drawpic(ppos, "gfx/sba1_quad", '16 16 0', '1 1 1', 0.7, 0);
else if ((poweruptime >=250) && (poweruptime < 300)) drawpic(ppos, "gfx/sba2_quad", '16 16 0', '1 1 1', 0.7, 0);
else if ((poweruptime >=300) && (poweruptime < 350)) drawpic(ppos, "gfx/sba3_quad", '16 16 0', '1 1 1', 0.7, 0);
else if ((poweruptime >=350) && (poweruptime < 400)) drawpic(ppos, "gfx/sba4_quad", '16 16 0', '1 1 1', 0.7, 0);
else if (poweruptime >=400) drawpic(ppos, "gfx/sba5_quad", '16 16 0', '1 1 1', 0.7, 0);
};

And later on I call the function in the HUD drawing function for the item bar, like this:

if (autocvar(cl_pwrtimer, 1) == 1)
{
if (sitems & IT_INVISIBILITY) PowerupTimer(pos+'224 8 0');
else if (sitems & IT_INVULNERABILITY) PowerupTimer(pos+'240 8 0');
else if (sitems & IT_SUIT) PowerupTimer(pos+'256 8 0');
else if (sitems & IT_QUAD) PowerupTimer(pos+'272 8 0');
}

Remaining question:
Did I get the timing right with the 30 seconds in the "poweruptime" calculations? 

Hey, NightFright!

Since you are working with HUD, maybe you can help me.

Do you know how to change a weapon's pic in the same HUD slot? Like in the Rogue's mission pack, you can select the nailgun and the lava-nailgun, and the pic changes.

Keep in mind that my CSQC knowledge is none. I only know how to work with QCs :P 

@ Spike:
While it works in general, there's definitely something wrong with the timer(s). Looks like if I save a game and reload, the timer seems to go out of sinc, plus collecting more than one powerup at once completely screws up everything (first powerup is reset and second one is shown almost depleted).

@ Tribal:
I am actually a newbie regarding HUD programming as well. I can identify certain parts in QSS's CSQC code and alter them, but writing code on my own is kinda tricky. 

OK, it seems like the timer the way I have written it right now is actually based on how much time passes BEFORE instead of AFTER picking up the item. The longer I wait with picking up something, the more it will deduct from my powerup counter. 

CSQC doesn't get saved. if you want things to be correct after saved games then you need to ensure things re-replicate properly.

ssqc (worldspawn or so):
clientstat(STAT_QUADFINISHED, EV_FLOAT, super_damage_finished);

csqc:
float timetillquadexpires = getstatf(STAT_QUADFINISHED) - time;
float timesincequadstarted = time - (getstatf(STAT_QUADFINISHED)-QUADDURATION);


whereas if you're trying to avoid ssqc changes, you can just compare your stats against the last frame, and if quad is obtained then `quadstarted=time;`, then you can use `float timesincequadstarted=time-savedtime;` in your draw code.
Just be aware of the issues that can result if you saved the game while holding quad, or switch spectator tracking, or die etc. 

The behavior is like this:

I save while standing in front of a quad. Then, I pick up the powerup immediately. Timer image progresses (seemingly) correctly.

After reloading, I wait before picking up the item. The longer I wait, the more the timer image has already progressed. That means it's counting time without me actually picking up the powerup.

Would this be fixed with that code, then? 

@NightFright

Thanks for your reply :)

I think i'll try to mess around with the code until I give up =D 

I still wasn't able to pull it off. While it is progress that the timer graphics now show up ingame, getting the timer to work in general has turned into the challenge. It would be a lot easier with involving SSQC. In client.qc, there are conditions for what to do when a powerup expires, e.g. if (self.super_damage_finished < time + 3). It would be cool to use this, just with time+25, time+20, time+15 etc. But I guess it's not that easy.

However, I want to avoid SSQC edits. As soon as you have to supply a specific progs.dat, the hud would break as soon as a mod comes with its own, which is the case quite often. On the other hand, csprogs.dat files are still rather rare, so the mod would work most of the time.