search

FortressOne / server-qwprogs

FortressOne qwprogs. Fork of Classic Fortress qwprogs. Fork of TF 2.9.
https://www.fortressone.org/
23 stars 16 forks source link

The Devil #605

Open Rickson-FOLD opened 3 years ago

Rickson-FOLD commented 3 years ago

This is a new class idea to stand in for the sniper: the devil.

I suggest we incorporate this class as is (because it's pretty simple--or with some modifications as you see fit) as a placeholder for the sniper. It will perhaps be used on occasion. Since the sniper never is, seems like it might be a good trade! Perhaps once a month or once a quarter someone else can come up with a better idea to replace the sniper slot, and The Devil could then be rotated out.

Being from Hell, he's immune to fire (flamethrower, incendiary rockets (he'll just use them to rj like a fucking witch), incendiary grenades and lava--but not friendly fire ;-). His weapon is a pitchfork (perhaps it behaves like an axe, or perhaps it has a half body length distance (similar distance as medic's aura or engineer's proximity to rotate sentrygun). That's all the offensive weaponry he has. 50 life, no armor. If he hits an enemy, they die (perhaps instantly or perhaps it takes 3 seconds and they're effectively tranq'd to kill them--allowing them to suffer but also seek retribution or spam a gren to help their team) (or we could have them take as much damage as a backstab from a spy--so enough to kill anyone who has 100% or less health). If he hits a friendly, they enjoy 2x speed for 3 seconds, then they die. His speed is 300, same as a spy. Maybe gren1 (2 max?) triggers invisibility for 4 seconds (though not while holding flag) (if so, he could go invisible for 8 seconds without reappearing by using them consecutively--and sucking up packs in the meantime, though not without sound, to possibly extend his invisibility). Maybe gren2 (2 max?) triggers pentagram (he's a devil after all) for 2 seconds. Maybe the last pack he picks up, whichever weapon was out, he can fire once with quad damage. Perhaps It would be a fun class because when a defense saw him, all attention would be drawn to him, similar to a spy.

drzel commented 3 years ago

I'm open to literally anything on sniper, since it's banned. Can be a playground for whatever you want. Something like this would take a PR though.

Rickson-FOLD commented 3 years ago

What exactly is a PR?

drzel commented 3 years ago

A pull request. A code contribution.

Rickson-FOLD commented 3 years ago

Meaning I learn how to code in Quake-C or something like that?

drzel commented 3 years ago

I could be wrong - but I don't see any of the devs jumping onto sniper work for a long time. Though in principle it sounds like something we could include.

Rickson-FOLD commented 3 years ago

So essentially you're saying I would have to code it myself to see it happen this year.

Doesn't seem like it would be too hard.

What's the first step?

drzel commented 3 years ago

You'll need to install git, then fork this repo and https://github.com/FortressOne/fortressonesv

You need to be able to compile this repo and run the server locally. Check readmes for instructions on this.

Then I'd look at sniper.qc and start to play around with it. Good luck, if you get stuck ask for help in #dev on Discord.

Rickson-FOLD commented 3 years ago

Oi vey!

How long do you think the setup process will take, before I look at sniper.qc?

How long do you think it would take someone like you, who is already experienced, to create the devil?

drzel commented 3 years ago 
        The setup process takes me about 20 minutes. If you’ve never used any of the tools it will likely take you a good 4 hours.The devil is hard to estimate. But with testing etc, 20 - 100 hours. For you I have no idea, if you have no experience at all much longer.---- On Tue, 30 Mar 2021 19:28:14 +1100  ***@***.***> wrote ----

Oi vey! How long do you think the setup process will take, before I look at sniper.qc? How long do you think it would take someone like you, who is already experienced, to create the devil?

—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe.