InsideQC Forums

Well, lately I've been running through all of the QC files and reading the code and learning from it (as well as removing un-used things) I've learned a lot about the syntax and how QC works, and it's been an interesting experience.. Well, lately I've been looking at the enemy QC files and their ...

It seems to me you dont have (yet) the required experience and engine knowledge to use the scratch code base. Maybe you should just take progs 106, strip out the unused parts and add your code ? At least would be easier to ask for help if something gets screwed.

You're probably right.. which is ...

- items_btl.qc (items.qc)
: at the top of the file - Line 1: void() UpdateWepaon;

This one doesn't even count as a call. It's just the function declaration for use further down in the code.
A function call will look something like this:


void blablabla ()
{
// some code
UpdateWeapon();
// more ...

You must ensure that updateweapon is called somewhere at every frame, so any weapon change (pickups, running out of ammo, etc) are visually represented to the player. Are you doung this ? And where exactly ?

OK, I'm calling UpdateWeapon (like W_SetCurrentAmmo in original Quake) in these places ...

the same? i maybe wrong. everything iv learned has either been from tutorials, or from reading the 1.06 qc. so i'd assume the best way to do things would be either similar or the same as ID.

I literally copy and pasted all of the need Parm code from client.qc (eg SetNewParms ect.) and adjusted it ...

OK, I think the problem is that it doesn't load the gun at the start of a map (like the axe/shotgun in original quake) I know how to change this in default QuakeC in client.qc with SetNewParms but how would I do this with scratch QC?

Here are the places that bprint printed nothing (meaning code wasn't executed)

void() UpdateWeapon = //like as W_SetCurrentAmmo in original Quake
{

self.items = self.items - (self.items & (IT_BULLETS) );

if(self.weapon == IT_BLUN)
{
self.weaponmodel = "progs/v_blunderbuss.mdl";
self ...

if (self.weaponmodel == string_null)
{
bprint ("YAY NO WEAPON MODEL!!!!!!11ONE");
}

Somewhere in your code should do the trick

Well, I placed this in my code and ran the came and no message popped up.. (YAY NO WEAPON MODEL...). So I was thinking that since impulse 9 isn't working either it's ...

if (self.weaponmodel == string_null)
{
bprint ("YAY NO WEAPON MODEL!!!!!!11ONE");
}

Somewhere in your code should do the trick

Well, I placed this in my code and ran the came and no message popped up.. (YAY NO WEAPON MODEL...). So I was thinking that since impulse 9 isn't working either it's ...

Assuming you're setting self.weaponmodel properly, and also assuming you don't have code somewhere that instantly sets it to null, I would be looking at whether or not your weapon models are positioned correctly. (i.e. internal to the model file) (try using your weapon models in stock quake, i.e ...

Hmm.. none of the code here seems to work.. (and yes I have checked my progs.src ) Impulse 9 didn't seem to work either, and I start with 0 ammo which is strange. :/

And I'm not just copying and pasting the code. I'm using it as a reference and reading it, and learning from it.

OK, so I have re-coded almost my whole mod onto Enders scratch QC tutorial. The only problem I have now is that I can't see any weapons. I know this obviously is because I haven't told it to spawn any weapons. But I'm not sure where to... I know that before QC was told to load the start weapons in ...

fteqcc -progdefs
will write out a progdefs.h file
I do urge you to consider the ramifications of the change. Your engine will not be able to load vanilla/third party mods, and your mod will not work in other engines. There isn't any going back (or there is, but there's a heck of a lot of work ...

Hello! :D I was wondering if there was a QuakeC Compiler that compiled the QC while also generating a progdefs.q1 file (for the engine).

I need this because I started re-coding QC from scratch since I don't need a lot of Quakes original code and it was taking up a lot of unnecessary space. (500kb ...

LESSON LEARNED ALWAYS ADD YOUR NEWLY MADE .QC TO THE PROGS.SRC!