Ranks and XP: Difference between revisions
From NEBULOUS: Fleet Command Official Wiki
mNo edit summary |
m →XP |
||
| Line 8: | Line 8: | ||
XP is gained via multiplayer games. Wins award 30 XP, losses and draws award 10 XP. XP is only awarded at the end of a match, so leaving early will deny any XP award. | XP is gained via multiplayer games. Wins award 30 XP, losses and draws award 10 XP. XP is only awarded at the end of a match, so leaving early will deny any XP award. | ||
There is currently no way to lose XP<ref>There is a function in game to deduct | There is currently no way to lose XP<ref>There is a function in game to deduct -60 XP if the player disconnects early, but it was dummied out as the dev couldn't find a satisfactory way to differentiate from a legitimate crash, or an intentional ALT+F4</ref>, any XP gained is permanent. | ||
== Ranks == | == Ranks == | ||
Latest revision as of 01:31, 1 October 2026
As players play multiplayer matches in Nebulous, they gain experience (XP) which translates to certain ranks shown in game. These ranks have no influence on gameplay except as a rough indicator of multiplayer playtime. They do gate rank-restricted servers, where players above the maximum rank can spectate but not play, and server autobalance uses rank to even the teams.
XP
XP is gained via multiplayer games. Wins award 30 XP, losses and draws award 10 XP. XP is only awarded at the end of a match, so leaving early will deny any XP award.
There is currently no way to lose XP[1], any XP gained is permanent.
Ranks
There are 11 ranks in Nebulous:
- Midshipman (MID) - 0 XP
- Ensign (ENS) - 100 XP
- Lieutenant Junior Grade (LTJG) - 500 XP
- Lieutenant (LT) - 1,200 XP
- Lieutenant Commander (LCDR) - 3,000 XP
- Commander (CMDR) - 6,500 XP
- Captain (CAPT) - 10,000 XP
- Commodore (CDRE) - 18,000 XP
- Rear Admiral (RADM) - 30,000 XP
- Vice Admiral (VADM) - 60,000 XP
- Grand Admiral (GADM) -120,000 XP
Notes
- ↑ There is a function in game to deduct -60 XP if the player disconnects early, but it was dummied out as the dev couldn't find a satisfactory way to differentiate from a legitimate crash, or an intentional ALT+F4
