Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The license was indeed for Windows so I got the game launcher from the website and now it didn't ask for a CD key. Still confused how this whole mess happened though, but at least I can actually download the game now! ^_^
Sadly steam and windows licenses are not the same and aren't compatible with eachother.
I'm glad the problem is fixed! Have fun in Eorzea! :D
If that's the case though, I'd just pick one of the two platforms, because otherwise you'd have two completely different accounts that would require you to buy the expansions and the subs for them both. I'd go for the platform you already have progress on.
EDIT:
As Alternity suggested, it is also possible that you indeed already have a second account for steam. In that case you may want to figure out which one is your "main"
I've never heard of SE deleting characters for inactivity. At this point if you really don't think you've another account, I'd really try to contact their customer support, there must've been something on their end.
A service account with the full version of FINAL FANTASY XIV and at least one character is required to log in to The Lodestone.
Please visit the Mog Station to manage your account.
Mog Station only shows my current character (the one I created today)
I had the same issue on another account and again on a new steam purchase. Apparently it didn't write the config properly. My solution was to run the boot exe from the directory, patch the game and then it fixed it itself after writing a new config file.
So it's not you. While their launcher is outside of steam is the exact same thing, apparently the config is not. That's about it though. Hope this helps you or anyone else in the future.