You can replicate this successfully every attempt with:
step 1: suicide, or already be dead
step 2: bind f [attack; edittoggle;]

I use this with my suicide fireworks, random fireworks appear out of nowhere :D

You exec both commands at the same time, which makes it think you are in edit mode when you are really dead, and you are dead, when you are really editing. You end up becoming alive in-between the two, inheriting the walking/jumping ability of play, but the invincibility of edit mode.

If you do this while players are on the server, they won't see you flying around when you edit mode. However new connecting players, will see you flying around, however they won't see you running around when you exit edit, they will just see your ragdoll flop to the ground.

Try jumping off the map, eventually you will be falling so fast that your pistol hudgun (or saw, you can only ever have 1 of the two in glitch mode), will literally detach from your hand and move up to the corner of the screen. It took me about 5~10m before I noticed the hudgun detaching. Moving the crosshair around in circles make the hudgun do circles around your hand :D

To escape glitch mode, either reconnect or toggle spec.

Edit: pistol glitch https://www.youtube.com/watch?v=2f0wjrnJrmc

You can't shoot people either, since the server is convinced that you are still dead. Same reason as the pickup thing: dead people don't shoot.

Do you mean CS_SPAWNING?
From src/shared/ents.h:
enum { CS_ALIVE = 0, CS_DEAD, CS_SPAWNING, CS_LAGGED, CS_EDITING, CS_SPECTATOR };

And what you describe sounds more like flying through oblivion when already glitched out...

your right its cs_spawning its been a min since ive looked at the code. And ya but you cant be shot at tho, even with an auto aimer. I do believe because when you are in the CS_SPAWNING state, the server is told you are at this infinite point in space. And you arent flying cuz you are not moving. You can tell by checking the campos.

If you wanna see this just change the kb in the Shoot() in side the weapons.cpp. Just take kb.mul(1000000); when you shoot you will be locked into infinite space. If you add an auto aimer in by:

//some were in the same function, preferable under the checks to see if you are allowed to shoot.
...
//note to is the pass in of the direction or the to vector of the players facing direction;
dynent *d = players[randint(players.length)];
to = d.headpos()
from = d.o;
..

This will cause your to shoot a random player ever frame (or every time you can shoot).

Combined these will cause you to shoot from "infinite space", with out being able to be shot back. Most the servers will try to solve this by randomly having you pop up around the map, (even tho you arent there). (Because you lied to the server and told them that you are shooting from the players feet to there head.

Note: Almost all the servers have solved this error and using any of this code will result in a almost near instant perma ban. So dont actually use this :)

chasester

Note: i just wrote this from memory it may not work correctly, but the concept is correct.

I think CS_SPAWNING and your "infinite space" thingy are two completely different things...
CS_SPAWNING is a thing of the server to protect you. I have seen this deployed as godmode hack before, but actually it is supposed to give your client a safe moment to pick a new spawnpoint after dying, receive ammo and health information and so on from the server and compensate possible lag from that.

Your "infinite space"... I don't know for sure, but moving with such an obnoxious speed probably fucks up something in the position vectors. When it is fucked once, it might transfer to everything position related. Your aiming fucks up, because the destination point of your shot can't be calculated properly, telekills and shit like that don't know what position to aim at, etc...