FTEQCC and bronzing characters .. how? [/b ?]
Moderator: InsideQC Admins
9 posts
• Page 1 of 1
FTEQCC and bronzing characters .. how? [/b ?]
Does FTEQCC support bronzing characters like FrikQCC by doing:
sprint(self, "This is /bBronzed/b text\n");
It may be either \b or /b in FrikQCC, I can't remember offhand.
Anyway, does FTEQCC support the FrikQCC method and if not is there some other way that works?
sprint(self, "This is /bBronzed/b text\n");
It may be either \b or /b in FrikQCC, I can't remember offhand.
Anyway, does FTEQCC support the FrikQCC method and if not is there some other way that works?
-

Baker - Posts: 3666
- Joined: Tue Mar 14, 2006 5:15 am
-

Error - InsideQC Staff
- Posts: 865
- Joined: Fri Nov 05, 2004 5:15 am
- Location: VA, USA
It may be either \b or /b in FrikQCC, I can't remember offhand.
FrikQcc uses \b if I remember correctly
Neurotic Conversions - New location: Update your bookmarks!
-

CocoT - Posts: 695
- Joined: Tue Dec 14, 2004 5:39 pm
- Location: Belly-Gum
Yeah, I know.
Fair enough, I guess I already had \s in fteqcc when I noticed frikqcc did the same thing for \b, so yeah, use \b for either qcc.
And basically just ignore the whole \s thing.
Yes, FTEQCC supports the QCCX/FrikQCC \b feature to bronze a string constant.
Adding a \b character in a string constant will do nothing itself, but cause all trailing characters (until a second \b) to be bronzed, as you described.
It is a backslash, which is consistant with C string markup.
(Although in C, \b is 'bell', and makes a noise instead of being printed, but mneh).
Note that this \b markup thing does not affect strcat/ceterprintX usage. Because that would quite frankly be magical. So stop being silly and moaning that it doesn't work, it never will do so stop moaning.
Additionally:
\0 ... \9 can be used to generate alternate numbers. \b\0\b can be used to get at the fourth range of numbers... Which I think are exactly the same as one of the others anyway, so mneh.
Additionally:
\xff is stripped out of strings by some quakeworld clients and not others. This is a fun character to use as the only character in your name. It can also terminate strings prematurely in some other engines. Use with caution, or humour.
Fair enough, I guess I already had \s in fteqcc when I noticed frikqcc did the same thing for \b, so yeah, use \b for either qcc.
And basically just ignore the whole \s thing.
Yes, FTEQCC supports the QCCX/FrikQCC \b feature to bronze a string constant.
Adding a \b character in a string constant will do nothing itself, but cause all trailing characters (until a second \b) to be bronzed, as you described.
It is a backslash, which is consistant with C string markup.
(Although in C, \b is 'bell', and makes a noise instead of being printed, but mneh).
Note that this \b markup thing does not affect strcat/ceterprintX usage. Because that would quite frankly be magical. So stop being silly and moaning that it doesn't work, it never will do so stop moaning.
Additionally:
\0 ... \9 can be used to generate alternate numbers. \b\0\b can be used to get at the fourth range of numbers... Which I think are exactly the same as one of the others anyway, so mneh.
Additionally:
\xff is stripped out of strings by some quakeworld clients and not others. This is a fun character to use as the only character in your name. It can also terminate strings prematurely in some other engines. Use with caution, or humour.
- Spike
- Posts: 2892
- Joined: Fri Nov 05, 2004 3:12 am
- Location: UK
9 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest

