Proquake Suggestions

[Lerster]

I know your busy baker, fixing stuff and adding stuff and whatnots.

However i just remembered something i wanted to suggest which is kind've random and useless atm.

However if it is moved over to every common server today it would likely be a very wanted and loved feature.

I was wondering if it was possible to have proquake catch (your ghostcode) upon connection to say 3wave at the moment... is the only thing that has ghostcodes that i'm aware of anyways.

However, i was wondering due to lagouts and occasional, lost connections that happens to everyone now and again.

Would it be possible to have quake catch that and even store it temporarily in a temp file, in the id1 or something and have it check that file upon connection and read it to the server like ghost 843 or whatever the ghost code is to use the code to get all your frags back.

I think if ghost code feature was ported to DM/RA/CA from 3wave it would be really cool. An would prolong the games, as there would be less rage quits from loss of connection and return to a middle of a rnd and to a team, without your frags.

The team would still have their current wins in most cases, but to fix the whole, oh FUCK ME I LOST MY FRAGS... mental derailment.

I'd love to see that feature added to the servers / and proquake client, and or other clients as well.

[s]This probably should've went into a suggestion forum topic thing. [/s]

Ah well... thats my idea.

It may be stupid and pointless, or it might be useful.

[Baker]

I'm open to all suggestions and I think this might be the best one I've ever heard.

Maybe a 5 minute grace period on reconnects? All the frags get saved.

About as interesting of an idea as I've ever heard. I'll need to think it though. It also might break stuff somehow (?).

I have to look at the [big] queue of stuff I'm trying to do and see where this kind of experimentation fits.

[Lerster]

Yeah, i don't doubt it would possibly break stuff as you have to (find/capture) the ghostcode upon server connect.

Provided the port from 3wave --> to every other server for the ghost code generator thing goes fine.

I figured a file to hold the ghost code would work better either txt (easiest) or binary file in the id1 that would store the ghost code when you connect, (provided the server has it) eventually be nice if all servers used a ghost code system.

Provided that feature is plausible/doable.

The reason i thought txt/binary file for it would be best is incase someones client crashes, as anyone that types quit (you could have a clear txt/binary) file statement in the client or whatnot... however upon error the file shouldn't clear then if they reconnect to that server.

An the client see's the ghostcode in the txt/binary it loads it automatically, and your frags and color return.

Then ya back in the game (provided the games still going) :p

Anyways, just a suggestion.

~Cheers. ^^

[R00k]

I barely read 2 sentences in Lerster's 1st post (im short on time), but besides setting a local infokey (like quakeWorld), it would be possible to have a client cvar cl_ghostcode for instance. In the mod, a stufftxt to client could set this.

The way ghostcode works is by assigning an alias ghostcode to a value. Then if you lagout and reconnect the server executes ghostcode and automatically puts you back into the game (my crctf anyways) crmod requires you to have to type it in. The problem is that if you client crashes your ghostcode alias is lost.

So either allow aliases to be save to your config.cfg or create a cvar and allow the mod to modify it's value. Or keep a pencil and paper nearby and write your ghostcode down.

And yes, ghostcode for CAx was/is on the todo list for CAx...