RE: A script engine written in QuakeC - Mr. I made it just for fun, does anyone know if something of this kind can be of any use? Print ( "Take one down, pass it around, you got " + buckets_of_oats(n-1) +
Wallstring = n = 1 ? "WAAAAALLLL!!!" : "wall" Print ( buckets_of_oats(n) + " on the wall, " + buckets_of_oats(n) + "!" ) Return n+" "+pluralize("bucket",n)+" of oats" Semicolons can be replaced by commas so it's easier to execute snippets from the console.įollows a simple script which gives a basic idea of the syntax: It has a C-like syntax, I guess somewhat similar to JavaScript.
Xonotic forums scripting code#
I've only tested it in server code but it should work fine in menu and client too. The interpreter is accessible via a command which can either run a file or a single line. It currently supports the following features: I'm not sure if this is an interesting concept or just a stupid idea.Īnyway, I managed to make it. Yesterday I thought it would be fun to make a script interpreter in QuakeC and so I did. +- Thread: A script engine written in QuakeC ( /showthread.php?tid=5121)Ī script engine written in QuakeC - Melanosuchus - 10-11-2014 Rather than trying to set moues acceleration at the system level, considering the situation, it might be more effective to adjust the acceleration on a per-game basis using in-game settings.A script engine written in QuakeC - Printable Version A program can also opt out of X11 pointer acceleration altogether. For example, Xonotic comes in two flavours for Linux: one is inked against libSDL, and one is based on OpenGL only and acceleration is different between those two, and both are different from standard X11 desktop mouse behaviour. Mouse acceleration in games can behave drastically differently depending on the libraries it uses (or does not use).
Note that input handling also depends on the kind of game you are playing, or rather its input handling implementation. Here is an extensive wiki entry on pointer acceleration with methods to try.
There are many settings to tweak when working with acceleration. It has almost nothing to do with the kernel but the X server. I have run 4.0+ kernels on this machine in the past with no problems so I'm just wondering why backporting might be discouraged. What's the general consensus on backporting around here? I'm a bit wary of the 'don't break Debian' thing, keen to keep it as vanilla as I can (although admittedly in some cases I've already broken that rule).
0 kommentar(er)
