qcexec: Execute qc functions from the console

[Baker]

Not new. But I don't hear it mentioned often -- err at all -- and want to draw attention to this this old tutorial.

Qcxec Tutorial --- execute QuakeC from the command line:

http://www.quake-1.com/docs/quakesrc.org/143.html

By the way, if anyone can shed like on great uses for this feature ....

[mh]

Hmmmm - I'd totally forgotten about that one. It would need to be extended to take function params of course, but otherwise it seems quite a neat little feature to have and if we could get a standardised version of it implemented in all engines we might have something useful for modders to take advantage of.

I'm thinking no more need to use impulses, just bind a key to a "qcexec" command.

[Spike]

most of the uses for this are superceeded by KRIMZON_SV_PARSECLIENTCOMMAND.
the remaining uses are for server admins only, but it generally doesn't permit remote admins.

it could be used for loading, say, frikbot waypoints, if the frikbot code was modified to use it.

as a tutorial, it demonstrates how to invoke QC code from the engine, and how to register new console commands.

[Baker]

I figured most uses of this would be as a QuakeC testing tool, never thought of the substitution for impulses idea (although I'm not sure that is a good substitute, heh).

[Downsider]

Just wondering, Quake only allows for one impulse per frame, if I were to use this, could I do multiple? And does it work online?

[Teiman]

Just wondering, Quake only allows for one impulse per frame, if I were to use this, could I do multiple? And does it work online?

I suppose it works serverside. I don't think it works online.
humm... as a substitute for impulse is sound.. unfortunally, compatibility > all. and since impulse is compatible everywhere, maybe qcexec for that only make sense on total conversions...

I dont know of any user case for this thing.

[mh]

I think it should work because the command is forwarded to the server, but I haven't tested.

[Team Xlink]

I have used that tutorial and it is worth it. It makes it very easy to test case specific occurrences in the qc code. Such as a function that says dominating when a player kills 6 other players with his boomstick in 3 seconds. I know it is a very unlikely case but it is an example.

I thought this was considered a standard already in the sense that most engines have it.

It is really useful.

[Downsider]

I think it should work because the command is forwarded to the server, but I haven't tested.

I thought that too.. But aren't only certain commands passed? No need for +mlook or "help" to be passed.

Either way the modification to get it to work should be nominal.

[mh]

According to the tutorial this one is. There's a Cmd_ForwardToServer in the function itself, and it gets a call from SV_ReadClientMessage. It would need to be forwarded to the server anyway as QC (aside from CSQC of course) only exists on the server.

[Lardarse]

I figured most uses of this would be as a QuakeC testing tool, never thought of the substitution for impulses idea (although I'm not sure that is a good substitute, heh).

That seems to be the biggest use of it. Would be very useful to have just for that purpose. Especially for testing edge cases...