From: Rudolf Polzer <divverent@alientrap.org>
Date: Tue, 18 May 2010 18:28:55 +0000 (+0200)
Subject: autocvars: undefine writing to the autocvar
X-Git-Tag: xonotic-v0.1.0preview~604
X-Git-Url: http://de.git.xonotic.org/?a=commitdiff_plain;h=9c814d087b81d4f4b5cdb345e644d6eb74a24ba2;p=xonotic%2Fxonotic-data.pk3dir.git

autocvars: undefine writing to the autocvar
---

diff --git a/qcsrc/server/extensions.qh b/qcsrc/server/extensions.qh
index ea6f0b068..33973f8e0 100644
--- a/qcsrc/server/extensions.qh
+++ b/qcsrc/server/extensions.qh
@@ -572,12 +572,12 @@ float(float a) tan = #475; // returns tangent value (which is simply sin(a)/cos(
 // string autocvar__cl_name;
 //NOTE: copying a string-typed autocvar to another variable/field, and then
 //changing the cvar or returning from progs is UNDEFINED. Writing to autocvar
-//globals is UNDEFINED.  Accessing autocvar globals after cvar_set()ing that
+//globals is UNDEFINED. Accessing autocvar globals after cvar_set()ing that
 //cvar is IMPLEMENTATION DEFINED (an implementation may either yield the
 //previous, or the current, value). Whether autocvar globals, after restoring
 //a savegame, have the cvar's current value, or the original value at time of
 //saving, is UNDEFINED. Restoring a savegame however must not restore the
-//cvar values themselves.
+//cvar values themselves. Writing to an autocvar global is NOT ALLOWED.
 //In case the cvar does NOT exist, then it is automatically created with the
 //value of the autocvar initializer, if given. This is possible with e.g.
 //frikqcc and fteqcc the following way: