Before upgrading, what to know before upgrading a Star Citizen ship is simple: record your current setup, define the result you want, and confirm your plan matches the ship and game version you’re using. That preparation gives you a clear baseline and helps you catch a mismatch before you spend time or resources.
Start with a short preflight note. Identify the ship and the component or change you have in mind, then write down the specific issue you want to address—for example, “I want this ship to handle the way I need during my usual flight.” Make the goal concrete enough that you can tell afterward whether the change helped, rather than relying on a vague impression.
Before you act, check that you are working with the intended ship and change, and consult current in-game or official information for anything that may depend on the game version. Don’t treat an older fit or behavior as proof that it still applies; use the separate compatibility guide for detailed fit checks. Keep this stage focused on readiness: component selection, comparisons, and purchase steps belong in their own guides.
A quick pre-upgrade check
Write down the ship and intended change, plus the result you hope to see.
Confirm the ship and change are the ones you mean to work on.
Check current information for version-sensitive requirements or behavior.
Before committing, review the exact ship or item shown in the confirmation flow. The official upgrade system does not allow downgrading to a ship of equal or lower value through that upgrade path. [1]
If the result looks wrong, pause rather than layering on more changes. Compare what you see with your original note, check that the intended ship and component are present, and retest your goal under similar conditions. If you still can’t tell what happened, keep your notes and check current official information or support guidance.
Your next step is to write down the goal, verify the component fits, and compare suitable options before making the change. Use the separate buying guide for transaction steps, and the prioritization guide if you still need to decide what to upgrade first.
Record your ship’s current setup and your goal
Before you change equipment, record what is installed, what you want to fix, and how you’ll judge the result. A clear baseline turns a vague “this ship feels off” into a useful before-and-after check—and gives you something to refer to if the change doesn’t behave as expected.
Make a quick baseline
Write down the ship’s name and the component you plan to change, along with the component currently installed. Add any visible settings that could affect your test, such as a selected mode or configuration. Keep the notes simple: “Ship: [name]; current component: [name]; setting: [what you see]” is easier to compare later than a memory of how the ship felt.
Use a screenshot if it’s quicker than typing, especially when the relevant details are spread across different screens. You can also note the date or your own test conditions for context, but don’t rely on a screenshot alone if it won’t show the settings you care about. A short written note beside the image can point out exactly what you want to compare.
Define what success looks like
Describe the problem in a way you can check after the change. Instead of “make the ship better,” try “reduce the time it takes to bring the target into view” or “make the ship easier to control during the approach.” Keep the goal tied to the situation where you notice the problem, not to a broad promise of improved performance.
Choose an observable result before you start. For example, note whether you want the same maneuver to feel more controlled, or whether a particular system should respond more reliably in your usual test. You don’t need a complicated scoring system; a few words about what you’ll look for are enough to keep the comparison focused.
If you’re changing more than one thing, record each change separately and avoid turning the test into a bundle of unknowns. That way, if the result is different from what you expected, you can trace it back to the specific change rather than guessing which part mattered. Before moving on, make sure your notes name the ship, the current setup, the intended change, and the result you’ll count as success.
Verify the ship, component, and game version
Before you change equipment, verify that you have the right ship and intended component, then check current in-game or official information for any requirements that apply. A quick check can help you avoid working from an old assumption, especially when ship or component behavior may differ between game versions.
Confirm the target
Read the ship and component names carefully before you begin. For example, if you own several ships with similar roles, make sure the ship you are preparing to modify is the one you have in mind—not another ship in the same fleet.
Then identify the exact change you intend to make. If you are looking at a component with similar names or variants, pause and confirm which one you mean rather than relying on a remembered label or an old note. Keep this check focused on the target; detailed fit checks belong in the compatibility guide.
Check current requirements and version
Use current in-game information or official information to check any requirements that apply to your planned change. If a menu, item description, or official page gives details that affect what you can install, use those current details rather than relying on memory.
Do not assume that a fit or behavior you saw in an older game version still applies. Mechanics can change between versions, so confirm the relevant information for the version you are playing before you proceed. If you cannot verify a detail, pause and check current information instead of treating an old setup or post as definitive.
Keep the fit check focused
A component’s name or its previous use on another ship is not enough to confirm that it is right for your current plan. Check the specific ship and intended component together, and consult the dedicated compatibility guide for detailed fit checks.
As a final readiness step, write down your upgrade goal, verify that the component fits, and compare suitable options before making the change. If you are still unsure about the fit, resolve that question before moving on.
Check the commitment before spending resources
Treat the confirmation flow as a final checkpoint: verify exactly what you are changing, and pause if the outcome is not clear. Before you commit, compare the ship or item shown there with what you intended; a mismatch is a reason to stop and reassess.
Check the target before confirming
Read the confirmation details carefully rather than relying on the name you selected earlier. For example, if you meant to change a starter ship but the confirmation shows a different ship or upgrade item, do not proceed until you understand why. This simple pause can help prevent a mistaken commitment.
Also check that the displayed result matches your plan. If the target looks right but you cannot tell what ship or item the transaction will affect, leave the confirmation unsubmitted and use the separate buying guide for the transaction steps. You do not need to guess your way through a flow that feels unclear.
Know the limit of the upgrade path
The official ship-upgrade path does not let you downgrade to a ship of equal or lower value than your current ship. [1] Keep that restriction in mind before confirming: if your intended result is a ship at the same or lower value, this path will not provide that result.
If you are unsure how the displayed target relates to your current ship, stop before committing and clarify the intended outcome first. Treat uncertainty about the current ship, target, or result as a signal to wait—not as a detail to resolve after the transaction.
A practical final pause
Before you submit, ask yourself: Is the ship or item shown the one I mean to change? Is the resulting ship what I intend? Do I understand what this confirmation is asking me to commit to? If any answer is no, pause and use the separate buying guide for help with transaction steps.
Once the target and result are clear, you can move to the next step without rushing. Keep your notes about the intended change nearby, and make the commitment only when the confirmation matches that plan.
If the upgrade behaves differently than expected
Compare your current setup with your baseline. Use the notes or screenshots you made before the change, then check the ship and component details you recorded against what you see now. If you were tracking a specific result—such as whether a system works as expected—compare that same result rather than relying on a general impression.
Confirm the game version and what is actually installed. Check the version you are playing, then verify that the intended ship and component are present and that the change appears to have been applied. If you expected a particular upgrade to be on a particular ship, check those details directly; the upgrade process calls for confirming the source ship and the upgrade details before applying it. [2]
Retest the original goal under similar conditions. Try to keep the test comparable to your earlier one, so you can tell whether the change helped or whether something else differed. For example, if you were checking a system during a routine flight, repeat that kind of test before drawing conclusions from a different activity. Avoid making several additional changes first: changing multiple things at once can make it harder to identify which change caused the unexpected result.
Keep your notes and look for current guidance if the cause is still unclear. Record what you observed, what you expected, and which version you tested; those details can help you retrace your steps. Check current official information or support guidance before trying further changes, and confirm the ship and upgrade details again if you are unsure what was applied. [2]
Make a short plan before you change anything
Make a short plan before changing your ship: write down what you want the upgrade to do, check that the component fits, and compare suitable options before you commit. That keeps the change tied to a clear goal instead of turning into a string of guesses.
Start with one practical outcome. For example, if you want the ship to feel easier to control, name that as the goal and decide what you will look for during a test. If the change is meant to solve a specific problem, keep that problem in view while weighing options; a component that looks appealing on paper may not address what is bothering you.
Before fitting anything, confirm that the part is suitable for the ship and the role you have in mind. A simple checklist can help: “Does this fit?” and “Does this option support my goal?” If you are uncertain about fit, pause and use the compatibility guide rather than relying on memory or assumptions.
Compare the options that pass that fit check against the same goal. For instance, if you are considering two choices to address the same handling concern, compare the details that matter to that concern rather than treating one as automatically best. The comparison guide can help you make that decision without turning this preparation step into a shopping workflow.
Keep the next steps separate: use the buying guide when you are ready for purchase instructions, and the prioritization guide if you still need to decide what to upgrade first. Before you make the change, return to your written goal, confirm fit, and compare the suitable options. A small plan gives you a clear next move: check compatibility, compare for your goal, then proceed when the choice makes sense.