A New "ProQuake" Is Imminent

[l33t]

I cant wait much longer for this release, I am dying inside please help me please... .. .

[TAXI]

is it possible to create a console command "saveconfig name" like in Q3 for those of us who don't know how to create cfg files which will save current setup into cfg. Or maybe an option somewhere that does the same... Just wondering.

[Baker]

is it possible to create a console command "saveconfig name" like in Q3 for those of us who don't know how to create cfg files which will save current setup into cfg. Or maybe an option somewhere that does the same... Just wondering.

Yeah, that's on my list. Maybe some sort of "backup" method too.

I cant wait much longer for this release, I am dying inside please help me please... .. .

Hehe, you won't have to wait long.

[Cataklysque]

repost

Reposting this from earlier this year

"1. Transparent HUD
2. Pointing in team msgs i.e. %x at %y in ezquake. For instance, I might be standing at quad on DM3, and if I point at MH at mound and hit a bind it would say "MH at Mound".
3. FPS tweaks (blood explosions etc)
4. Show speed command
5. In game funname creation"

[Baker]

A show_speed command and making it easier to make cool Quake names would be fine to add in this. I love the show_speed command in JoeQuake. #3 is something for certain I know J.P. Grossman never would add to his engine.

#1, possibly as an option. I've already played with that idea. #2, seems unlikely. I don't want to add anything to this that gives someone an advantage over ProQuake 3.50 other than convenience and bug-fixes.

[Baker]

Alright, it appears I have managed to fully fix the FOV "bug" in ProQuake.

I am hoping this fix works for everyone. The fix itself is from aguirRe's Enhanced GLQuake. I studied his engine and Tyrann's, which both have FOV fixes and I think I did this properly.

With this done, I'll wrap up the final touches and release what for now will be called "Unofficial ProQuake 3.60" within the next 12 hours.

[l33t]

you da man

[Cataklysque]

Baker,

Good stuff, thanks for the reply. Basically I'll be satisfied with anything you can borrow from ezquake or fuhquake.

[Baker]

Baker,

Good stuff, thanks for the reply. Basically I'll be satisfied with anything you can borrow from ezquake or fuhquake.

Yeah I think your feature ideas are great, but a couple of those would be a better fit for engines like Qrack/JoeQuake/DarkPlaces that don't have the old school 1999 Quake feel.

I personally really love the feel of FuhQuake, and would love to see some of the things not already adapted in Qrack/JoeQuake put in those engines.

[Cataklysque]

I agree, I'd like to keep the same raw feel to it. But, ezquake and fuhquake were designed with 1on1 and 4on4 gameplay in mind. Most features will port very well to Proquake, considering it's mostly used for 1on1 and 4on4 gameplay.

I mean there are some things that just have no place in proquake, (custom texture colors come to mind) but a good portion of it would be great.

If I didn't mention it already, thanks for doing this.

[Mindf!3ldzX]

i hope you plan on releasing the source code, we don't want another trujen fiasco.

[Baker]

i hope you plan on releasing the source code, we don't want another trujen fiasco.

Of course. I would be the ultimate hypocrite for the countless times I've ripped on XQuake over the years if I did that.