You may well have seen this on other sites, but no-one seems to have stated it here.
If you are Australian, or European (including UK) - you cannot pay for a Guardians License. The option simply does not appear on the PlaySEGA website for you to pay.
Sega have just added 'US ONLY' to the main page too, a bit late there, considering a good number of importers have probably had their copies shipped.
You may well still be able to pay if you can find a willing US friend though.
I don't think this is the case for PSU360 - as its listed on the marketplace for everyone. But I don't know if NTSC PSU will run on a PAL 360.
I don't think this will cause a problem. They can just use a credit card for payment.
Darkwolf30 Wrote:I don't think this will cause a problem. They can just use a credit card for payment.
If you're on the PC/PS2 version, you can't really.
I have an account on there already from my BB days - the option to purchase a Guardian's License simply does not appear for me. Americans get the choice of PSU or BB. I get sent straight to BB.
Setting up an American account might work, but that might require an American credit/debit card - which still screws a lot of non-US people.
Oh in that case it might be a problem
I just vomited up my heart onto my keyboard...
Money Wasted... Time Wasted... ¬_¬; what's SEGA's problem
Every EU player that imported should email sega.
They'll probably just give you some automated reply... that's what they always did when I sent e-mails for tech support back in the day... despite specifically listing that one of their e-mails was totally not part of the problem... and showing that e-mail... they sent the exact same thing with different wording.
Face it... Sega's customer support hasn't precisely been very "notable" in the past several years.
Yeah they always sent me the same automated reply when i tried to fix a problem on BB.
With me, after 6 phone calls and 3 e-mails... they still couldn't give me any decent ideas on how to fix me constantly getting Error 102 on their servers... turns out the problem was THEIR adjustments to how PSO+ handles DNS calls as opposed to PSO... cause when I used a small DNS program to convert it back to the way it is in regular PSO... it worked 100% of the time... too bad I found this out AFTER 6 months of the constant 102 errors...