That's a lot of actual bugs  

Anyone who replies, look at his post, those are bugs NOT personal preferences of how the game should be. In fact I'd recommend to moderators that anyone who doesn't post bugs and posts personal "bugs" instead have their post deleted so this thread remains clean.

As for the SDK, we all want it, I really want it so I can add customisation to teleport effects. Don't expect it any time soon tho, the rate LEC are going we'll all be measured for our graves!

If it's helping anyone, here is the color scanner I wrote for xmod a jk2 mod.

Code Sample

void wCleanName(char *name, char *out, int outlen) { qboolean valid = qfalse;    char *wp = out, *rp, *rap;    //write, read, and readahead    for(rp = name; *rp == ' '; rp++);   //eat leading spaces    while(*rp)    {        if (*rp == '^') //oh no, we have a color code        {            for(rap = rp; *rap && *++rap == '^';);  //find the first non^            if (*rap <= '7' && *rap >= '0' + !x_showblack.integer)  //if it's a valid color code (between 7 and 1 if x_showblack.integer is 0, 7 and 0 otherwise)            {                if (wp - out < outlen) *wp++ = *rp; //copy one ^                if (wp - out < outlen) *wp++ = *rap;//as well as the number            }            rp = rap;   //skip the color string... it has been written if it's a valid one        }        else        {            if (wp - out < outlen) *wp++ = *rp; //length checking... just to make sure we don't run over the edge of the out string and crash the server... o_O        }        if (*rp) rp++;  //read the next one if there is a next one... (a bad color string at the end will cause rp to point to the ending null char)    }    while(*--wp == ' ');    //from the end of the line, look backwards for the first non-space.    *++wp = 0;              //go back to the space and make a null character (this clips trailing spaces)    rp = out;    while(*rp)    {        if (*rp != ' ' && *rp != '^') valid = qtrue;        if (*rp == '^') rp++;        if (*rp) rp++;    }    if (!valid) strcpy(out, "Padawan");   //if, after all that, we're left with nothing, name them Padawan }

This code is free for anyone to use for whatever they want.

Putting this back up as it's not a personal issue. It's a real bug in the game!

- Returning saber suck in floor (makes looped clanging noise)
This time I have included a screenshot of the saber suck in the floor.  It loops the clanging noise and spins on the ground never comming to rest.

- Can't get off mounts or leave guns!
During gameplay there are major issues of players unable to dismount bikes or leave map entity guns right away.  This causes for not so nice deaths when you are trying to jump off an about-to-explode bike!

- Major glitch allowing players to enter solid structures (on ctf maps even!)
There is an issue where a player can use jump+duck+forward (tapping all) to step into solid brushes on various maps.  Below I pointed out 1 of them.

repeat jump+duck+forward and eventually you get

note: I did not use noclip mode to enter this area!

Any chance of making this sticky so duplicate topics don't pop up?  Feel free to delete this reply  

- Weird flashy colors
Sometimes when I'm playing and walk near a wall a bunch of spectral colors flash all around and makes for people to be able to see me easily. Usually when I turn my saber off or lose the flag in CTF it goes away, but sometimes it stays.

- Elevators
Especially an issue in mp/ctf1 where you need the elevators to reach your objective, and they take 5-15 seconds to move. Also, when someone is standing over where the elevator will go at the top the elevator stops and goes back down.

- Speeder problem in mp/siege_desert
Sometimes in mp/siege_desert when another player goes on a speeder the pov switched between that player and your player rapidly, causing it extremely hard to move, see, and complete objectives. This happens rarely, but is annoying when it does and makes you have to reconnect to lose it.

BaD_HeX: I've had the same issue and I believe it is related to someone spectating you while you exit a speeder.  Both the spec and the player get stuck in a camera loop and need to reconnect to correct it.

Is it going to be possible for them to fix that? Because I hate having to reconnect. Wastes valuable playing time and someone may take your spot. Would that be an error in coding?

It should be totally possible when they track down exactly what is causing the issue.  If it is indeed spec related then it should be as simple as fixing the spec saber bugs in jk2.