JJnet's forum

Borgia convinced me that we should have an actual proper [i]guide[/i] to CTF codes rather than a long list that would just confuse new members, so I think I'll just barge in and simplify the codes list to what can be described as a language: [b]1[/b]/[b]2[/b]/[b]3[/b] ([b]4[/b]/[b]5[/b]) = Health (as information) [b]H[/b] = Health (as a request) [b]E[/b] = Flagholder [b]F[/b] = Other enemy (I'm not sure why it isn't the other way around) [b]S[/b] = Ready to score, can be used as a verb [b]R[/b] = Ready to recapture, can be used as a verb [b]D[/b] = Defending own base, can be used as a verb [b]A[/b] = Attack enemy base, either to become [i]R[/i] or to capture the flag that isn't already held. [b]C[/b] = Carrot [b]F[/b]/[b]H[/b]/[b]NA[/b] = Ammo, for informative purposes, with prefixes Full, Half, and No [b]DD[/b] = Don't Die [b]T[/b] = Taken, used to refer to ammo [b]N[/b] = No, used to refer to missing pickups or to reverse the meaning of another code [b]hunt[/b] / [b]kill[/b] = Hunt down the flagholder [b]?[/b] = As with English, used to change a code into a question or request [b][space][/b] = Used to denote separate thoughts/codes, can be irrevelant when used with actual English words Everything from there is a simple matter of arranging these around to form the codes, and there's really a lot of different ways to be done, though using regular words from time to time can be necessary. If I'm the flagholder and I'm on 2 health while I know the enemy is on 1, the following conversation could take place: Me: c? Teammate: nc Me: s2 e1 hunt Or in a 3v3, both flagholders are 1, but I want to pull off a risky maneuver: Me: h? Flagholder: 1 Me: eh? Teammate: e1 Me: go s Me: r3 fa Teammate: csoon Teammate: camping c This sets up for my flagholder to stay ready to score with 1 health while the enemy flagholder is roaming for the teammate-guarded carrot and I'm ready to recapture at enemy base with 3. Or we just roasted the enemy flagholder and we're trying to set up a score: Me: go s Me: d3 fa Ammo powerups are mostly referred to by their first initial, and Loon's list summarizes it pretty well. It's important to be able to type these out as you take the ammo pack or notice an enemy taking it, as knowing what firepower they have can dictate how much the team is able to extend or push by. Underlines denote the more common/used abbreviation: [b]b[/b] = Blaster (if conflicts with bouncer, use [b]bl[/b]) [b][u]b[/u][/b] = Bouncers (if conflicts with blaster, use [b]bnc[/b]) [b]i[/b] = Ice [b][u]s[/u][/b] = Seekers [b][u]r[/u][/b] = RF Missiles [b][u]t[/u][/b] = Toasters [b]p[/b] = Pepper [b]eb[/b] = Electroblaster Attaching the [i]t[/i] suffix to any of these initials, i.e. [i][b]st[/b][/i], [i][b]rt[/b][/i], changes it into an informative statement in which someone (most likely you) has taken the powerup specified. Further attaching a player prefix to this code specifies who has taken the powerup in question, i.e. [i][b]ebt[/b][/i], [i][b]ftt[/b][/i]. Don't forget the [i]n[/i]-prefix for stating that the powerup is gone; though for less ambiguity you might want to elongate the powerup's name for [i]n[/i]-, i.e. [b]nbnc[/b], [b]nseek[/b]. There's one (two?) more commonly used term, but it's less of code and more of shorthand, used before a game actually starts, when you have time to talk about what you plan to do: [b]a/d[/b] (?) = Attack/Defend (?) (2v2 only) [b]a/d/r[/b] (?) = Attack/Defend/Ready (?) (3v3 only) It's a question to ask who in the team is prepared to do which task during the opening minute, where Attack is the go for the flag, Ready is to stay behind once the flag has been captured, and Defend is to defend the base as from the prior two tasks. Lots of players may develop their own way of typing these out during games, almost like a personal 'accent' of sorts. Just remember you're still speaking the same basic language, and you should be fine.

Sean, you just gave a definition of space! here's some more CTF codes ;) pos = position (x,y coordinates) w = wait nvc = no f*(king carrot ce = camp electro get c = get carrot get a = get ammo get r = get ready na = no ammo ns = don't be on base ne = enemy team doesn't have flag. (I only used this once but it seemed to make sense at the time) gj = good job (to your team) $ = random spam. (this code is m0ti's invention) enub = enemy is a noob. Playaz, I just wanna let u know - all your contributions are really appreciated!

Instead of "eh" (which I never saw in use before) I'd rather just say "E?"

I use ''E?'' or ''E???'' when I want to know Enemy's health. I once got an answer on that ''Yes''. I asked what yes, and he said, yes, E's got the flag. (facepalm) Btw, this one is really important, gj Sean! F = Other enemy (I'm not sure why it isn't the other way around). I use it a lot, but somehow forgot to mention.

E was created first, short for Enemy VS used to use F instead of E for some reason At some point or other I thought it'd be useful in 2v2 to know the health of both enemies, so I just differentiated the two, using the less common letter for the less common purpose! "A" in your guide misses the meaning "get r", Sean

Short annotation: If said by the flag holder, "ns" may also mean "I'm no longer on base, don't expect me to score now"

[quote="Sean"] Me: c? Teammate: nc Me: s2 e1 hunt[/quote] That's the major issue I'm dealing with (but that's probably because I'm still quite inexperienced): typing the codes. Sure, shift+T+R3 for instance is relatively easy to do while running around or camping near a base. But something like s2 e1 hunt is impossible to type quickly while playing. It's already hard to do it when I'm alone in CD, can you imagine what it would be like if there's a game going on? I have no control over my bunny, so while typing this the situation might change. I think the codes have to be as short as possible, like shift+T+3 (or whatever health you have), shift+T+BT (or whatever type of ammo you've taken), shift+t+R3 (when ready to recapture once the flagholder has indicated his/her health) etc. Besides, conversations (although important) might distract from the game. That's something only the experienced people can do. I can't focus on the game and have a code-conversation going on at the same time. A for Ammo? It can also be used to signal you're going to attack the enemy base, right? Perhaps you can make a difference between the two uses of 'A'. You have made a great guide, Sean ;), but I see that many people propose small additions or other uses of codes. I think it will be difficult to create one, coherent list of codes that everyone can agree with. Oh well, as long as everyone knows the basics and uses them the same way, we'll be fine indeed.

[quote="Borgia"]A for Ammo? It can also be used to signal you're going to attack the enemy base, right? Perhaps you can make a difference between the two uses of 'A'.[/quote] A on its own is used to refer to attacking the enemy base. When you're referring to ammo, you'll be using a prefix: [quote="Sean"]A = Ammo, for informative purposes, with prefixes Full, Half, and No[/quote] FA, HA, NA :p

[b]rush[/b] - [i](said to your flagholder when enemies don't have your flag)[/i] = go to score before opponents can capture our flag. Can be made into a [size=24][color=cyan][u]double rush[/u][/color][/size] or, in theory, a... [quote][code]Triple SBv2 Rush[/code][/quote]

[quote="Borgia"][quote="Sean"] Me: c? Teammate: nc Me: s2 e1 hunt[/quote] That's the major issue I'm dealing with (but that's probably because I'm still quite inexperienced): typing the codes. Sure, shift+T+R3 for instance is relatively easy to do while running around or camping near a base. But something like s2 e1 hunt is impossible to type quickly while playing. It's already hard to do it when I'm alone in CD, can you imagine what it would be like if there's a game going on? I have no control over my bunny, so while typing this the situation might change. I think the codes have to be as short as possible (...) That's something only the experienced people can do. I can't focus on the game and have a code-conversation going on at the same time.[/quote] That's something that no one around struggles with after a decent amount of time playing JJ2. It's like, that single [i]s2 e1 hunt[/i] isn't arranged in my mind as a series of words in a normal language, instead it's a VERY well-rehearsed routine which I can type out in just under a second and leaves minimal interference with actual play time. Basically, practice :P Another tactic to use for a series of thoughts is not to stop for the whole second to arrange a longer string of codes but to stop, quickly type out one section, move a bit, type the next one, move again, type, go back to playing. This can be useful in certain situations if you [i]really[/i] need to keep your momentum, as inertia's coded into the game and you'll keep some movement during the typing process. It's also common to type the codes out when you're falling, or really just any opportune moments in-game where the loss of a second of active participation does not result in any loss of productivity. I've fixed up the guide a bit to correct some ambiguity errors, should be clearer now.

@Sean: Thanks for the advice ;).

Sean already pointed it out: [quote]E = Flagholder F = Other enemy (I'm not sure why it isn't the other way around).[/quote] I don't know if someone else already commented on this matter, but I should point it out again. To me, it makes way more sense if F is used to refer to the enemy Flagholder, and E to the other enemy/enemies. Does anyone agree?

It does, but the thing is that "e" is short for "enemy flagholder" and "f" was just added up to it later on [quote]E was created first, short for Enemy VS used to use F instead of E for some reason At some point or other I thought it'd be useful in 2v2 to know the health of both enemies, so I just differentiated the two, using the less common letter for the less common purpose![/quote] this gave me a good laugh when I noticed it just now: [quote]E1 OR LAG (exclusive to Grytolle) = E1 or lag.[/quote]

Cs - can also mean Candy Soda or chocolate soda

Instead of using 'E' for Enemy Flagholder, is it an idea to use EF for this instead and the E to refer to the non-flagholding enemy/enemies?

It is an idea, but since the allocation of these abbreviations hasn't changed for an eternity its implementation would cause sheer confusion :xD2:

EF = enemy fighter / enemy flagholder / enemy foe

The words 'enemy' and 'foe' basically mean the same thing, so there won't be any confusion there I think :P. And isn't it quite obvious that the enemy is fighting you? I mean, you don't run into an enemy idler, popcorneater, magazinereader or what :P. Besides, the flagholder fights too, so EF meaning Enemy Fighter is too ambiguous. No, EF stands for Enemy Flagholder, and even though people are used to the current E and F, I think it shouldn't be that hard to learn and remember. It may take time, but I have hope ;). Oh, and by the way: Happy new year everyone!

Fighter can only be used in 2v2s and its 100 times more unimportant as Enemy flagholder. Besides, especially in levels with multiple carrots, one should just focus on E as F information gets outdated quicly. If you need to use it theres always F.

[quote="Borgia"]And isn't it quite obvious that the enemy is fighting you? I mean, you don't run into an enemy idler, popcorneater, magazinereader or what[/quote] I would expect to run into an enemy camper who goes idle or away from keyboard who hasn't yet been found, in which case they might be fighting a power up spawning point. I guess then - ec(x) - enemy camping a variable fc(x) - fighter camping a variable go/geaux (as in - go somewhere else) - don't have the same screen as me / try to be fastest to the C

Laz had a convincing explanation about the use of E and F. E is Enemy, the most important, main target in the game because he/she is also the flagholder. F is the 'normal' enemy, referred to as Foe (or Fighter according to KRSplatinum, in that case I can imagine EF might cause some confusion). That makes sense. Okay, I think I'll just drop my EF thing altogether and stick to the use of E and F. I've noticed, though, that F isn't much used anyway.

It is only useful in 2v2s when you want to kill E and make sure F doesnt cap or caps with low h.

Playing 2v2 without reporting F will make you lose many an even game :p The information rarely if ever gets outdated if you also communicate correctly about the carrots in the map. Perhaps in maps with 3 carrots or more what Sven said becomes an issue, but luckily such maps are rarely played. In 3v3 F is still useful, but it isn't as accurate, because it becomes ambiguous when there are two Fs on the other team. For that reason people use it a bit less, and use stuff like "gry1" instead when they feel a very urgent need to report something. You can you can however still use it to refer to both F's at once "flow" "fs low" "all f low" end up meaning pretty much the same thing, though the first option could just refer to one of the two enemies without further specification, semi-useless as such a report may be

What I do use in 3v3s occasionally is FST or any pu for example to warn our flagcarrier an enemy foe/hunter took a power up. I don't specify which enemy but our flagcarrier is at least warned that he/she can die a lot faster. Same goes for FCC or FCS. I dont think I need to tell who is camping cause that doesn't usually matter. It's just so our flagcarrier knows not to go to the carrot or to hide.

/ - and/or for example: c/nc? s/dd bt/st come - find me (usually at the carrot so u can give ur teammate a free carrot)