Adding Rain To Vanilla Quake and Kurok

[thommoboy]

How would i go about doing this?

[Spirit]

You are being a leecher. Asking for people to work for you without displaying any self initiative or willingness to investigate. Please stop that.

[Baker]

http://www.geocities.ws/lordasaki/mods/rain.txt

http://www.geocities.ws/lordasaki/mods/rain.zip

[ @ Spirit, I really think a severe problem is that there really is no way to get the slightest foundation to how Quake modding works without asking someone somewhere a ton of questions. It is unfortunate. I recall asking a trillion stupid questions once upon a time, and it wasn't fun not knowing even the answers to some simple questions. I agree with your sentiment, but then again maybe in retrospect the amount of info your absorb just being around is rather substantial. As an example, you've done a ton of "engine versus engine features" and "software versus GL" projects which were things that even playing Quake for 8 or 9 years, I didn't understand or think of. There needs to be a better way to tell someone new to the idea of modding Quake what to do and how things work. ]

[As an example, I was not able to locate the above files easily with a Google query, I had to heavily "shape" it with conditions to find it .... i.e. Google: "rain.qc" "quakec" <---- nobody is going to do that by chance even with an honest attempt.]

[goldenboy]

I think that was a bit overly harsh Spirit. Seriously... he's just asking questions. Give him a break.

[Baker]

[Seven]

Hello,

I always have this picture in my head when I enter this forum:

Inside3D - Knowledge is power

But what if this knowledge is only in some peoples head ?
You can only access this knowledge by asking questions.
Just like Baker said:
You HAVE to ask questions to understand things sometimes.
And thanks to all the wonderful members of this forum,
the knowledge is given to those in need.

I think everyone had to ask questions (even Spirit) when first entering the Quake universe.
Of course, trying to find out by reading and using the SEARCH button by themselve is the best thing to do.
But many things got lost (like Baker said), and asking has become more and more necessary.

Kind regards,
Seven

[mh]

It's also the case that today's leecher is potentially tomorrow's awesome mod. Once someone builds up a critical mass of info, who knows what they'll do? It might never happen, true, but the possibility that it might happen makes it all worthwhile.

[dr_mabuse]

Be carefull with that on the psp, i got buffer overflow on the test map xD

[Nahuel]

i remember in my first questions the people of this forum answered things like "try with CSQC", well I'm pretty frustrated with that, but now I can say that I understand many things from qc I never imagined that before knowing. I learned a lot about CSQC!!! I think the qc is easy, requiring only adequate time to learn. This forum is great:) and while spirit and baker are quite right in both points of view, I suppose it's best to help the questioner (leecher or not). And Baker gave his help and then that's great!! it is also frustrating to want to say something to a person who is not fully oriented or or unresponsive answers help with a simple "thank you". But I think if you take the time to answer you can give the right help, and the forum does it job, and other leechers will read about !!!

[WickedShell]

Maybe it was just me but when I first came around, the most helpful tutorial's were Ender's Scratch . It may have been the most helpful because I could already program, but stepping through those tutorials, explained a lot of the basics, and removed a lot of the quirk's that you see in the developed code, and shows you what callback's the engine expects/requires. The only work I've released here (a terrible hook mod), was based off of that, and was entirely a learning experience, but from the end point of that scratch tutorial, I gutted everything I didn't want and forced myself to implement all the func_'s /entity's I needed without looking at the original quake code, past establishing what each func_ is really supposed to do.

Nahuel's point about csqc is valid. Now that I know what it is I want to use it almost to much But there was a real problem with learning CSQC, I had to go find an old old tutorial from Urre at a quake expo, that had some problems. And fte's csqctest failed really really badly in darkplaces, making me think it was useless till I switched to running it on FTE, at which point it was a helpful reference again. (Mostly for porting my code from darkplaces csqc to fte csqc). But csqc primers are pretty harsh.

My experience (and maybe I'm the odd ball), but reading through the old posts, and exploring that has proven quite profitable, and when I have an issue I usually ask it in IRC, but specific issues tend to receive useful help. (IE "spoike! I made fteqcc seg fault by calling a function I defined, what did I do/how do I fix it?" and you then get helpful answers back, incidentally I had failed to comply with either NQ or QW CRC's so it got all angry but I didn't know what I was doing). But you guy's aren't terrible at welcoming people (or at least I didn't feel all rejected, even if I was making some not so great stuff).