How to avoid the worst bugs in Star Citizen (as of v4.1.0)
Mostly the same as 4.0.1 with a few new ones (game crashing/ATLS crimestat issue).
The first trick you'll need to learn is how to Server/Region Hop. Some of the worst bugs require just leaving the current server and going to a different one.
To force a server change you'll need to exit back to menu and change your region to something else.
Note: If you attempt to start the game in the same region, the game leans toward placing you in the server where you've been most recently.
Elevators
Bed log as often as you can to avoid current hangar instance issues and set your spawn at a less popular station. Most hangar instance issues have been fixed by now, but they occassionally pop back up in busier stations (such as Checkmate) on certain servers.
If the elevator to your hangar isn't working, try all the other elevators. If none of the elevators work, you'll either need to go to a "Pad" and hitch a ride with someone, or server hop to find a working server.
Don't press up against the door when waiting for an elevator to arrive, it might push you out of the station as it physicalizes.
if you're encountering frequent game crashes...
Only use the ASOP terminals inside of your hangar to spawn your ship.
To avoid losing cargo, always store your ship (completely) before leaving your hangar.
To avoid losing refinery jobs, retrieve your ship first, then store it before collecting any cargo from the refinery.
If you collect a refinery job and the cargo doesn't appear on the ship, store and then re-retrieve the ship to get the cargo to appear.
Always remove your undersuit before leaving prison (legally), or before turning yourself in.
Whenever warping around a planet ALWAYS be ready to cancel the warp by switching from NAV to SCM.
Don't shoot/destroy any ATLS when in Stanton and near an active Comm Array or you will get crimestat.
If you come across an invincible player, use a takedown move, then again while they're on the ground.
if you come across invincible/desynced NPCs, use a takedown move or...
Always turn off engines when landing anywhere with gravity.
Always leave engines on when exiting your ship anywhere without gravity.
Don't Alt+F4 in hangars ever.
Don't sprint into an elevator full of other players.
Do not land on asteroids (particularly the ones outside of the Pyro asteroid bases).
How to not die when using the ATLS.
Jump when exiting a structure at any Pyro outpost. Marked as fixed now.
If you're unable to jump through a wormhole...
Store and then retrieve your ship after refueling to avoid being stranded without fuel mid-jump.
If you get stuck in a wall/rock...
Don't send/receive party invites while the sender/recipient are in an instanced location (any elevator or hangar) or else you will not see their marker.
Don't stand up immediately from your seat the second you enter quantum.
Don't suicide immediately after setting your spawn to a different hospital/location.
If you can't put a fuse into a fuse door...
Refueling/repairing "landing" screen issues
If you use Nvidia DLSS, hold off on updating to Nvidia app version 11.3.01.218 since this will break DLSS in Star Citizen, stick with version 11.2.01.337 for now.
Good list. I can confirm most of those issues and workarounds.
The only thing I would add is a caveat to this rule:
Always leave engines on when exiting your ship anywhere without gravity.
Gravlev vehicles burn fuel like it's going out of style. There was an IC, but CIG archived it as not a bug stating it was a feature change request. I disagree with that assessment, but it is what it is. Regardless, for gravlevs I would suggest turning off engines when exiting in zero-g if you plan to be off of it for more than a few seconds. Otherwise, you might find your vehicle has an empty fuel tank when you get back on.
Good point, I usually only use gravlev vehicles in zero-g for taking out comm-arrays (and it only takes a few minutes to hack), so I haven't run into this issue yet.
I'll add the info into the list. Thanks!
Edit: Granted, I haven't hacked any arrays in 4.1 so if this is a recent fuel nerf, then I'll definitely need to change my tactics here.
To be honest, I was being a bit hyperbolic about the "few seconds" thing. It doesn't drain down that quickly, but it does drain noticeably even when not moving. The problem is, as your list suggests, a planned eva of only a few minutes can turn into an extended ordeal if you run into bugs or other problems and depending on the distance you have to travel that little bit of fuel saved by shutting off the engines could make the difference when you finally make it back into the pilot seat.
The fuel issue was there in 4.0, but if you were using the gravlev bikes sparingly then it wasn't that noticeable. I only first noticed it when I needed to travel a good distance (>30km) over rough terrain on Bloom to reach a hostile settlement that was surrounded by an extensive array of defensive gun and missile turrets. Halfway there I realized it was going to be a one way trip due to my vehicles quickly dwindling fuel reserves.