I broke down and put in a support ticket, on the off chance they'll bump my rank (I'd think it should be easy to check the logs and see the giant pile of advancement missions I did today). Not super hopeful, but meh.
I had the same kind of thing happen. Ran three imperial navy ascension missions trying to get to baron from lord. I know they said imperial. It was from an imperial station in an all imperial system. Yet some how, I am now a federal "cadet" even though I dislike the Feds more than I can explain with words. The third one did finally give me Baron rank but I still want nothing to do with the Federation. I would like my cadet rank removed.
Thank the ancient Sol God!
After the most recent update (1.3.02?), I accepted an Empire mission to move from Outside to Serf and it worked!
The Empire likes me, they really do!
Sorry to hijack guys, I'm a noob at this whole PP thing. But I am currently p!edged to the empire so you might be able to help.
Firstly, do I need to do the tasks in order? I.e preperation > expansion > control ? The reason I ask this is that me and a friend pledged at the end of a cycle, we were working towards preparing Grovichun - cycle ended - and now Grovichun is under the expansion header, do we continue onto helping the expansion or return to preparing another system?
My second question isn't really important but I took onboard 10 sealed contracts, did I pay for them? between leaving to get them and returning to deliver, I lost 100kand I didn't take notice whether the contracts costed anything.
Thanks in advanced, I hope this is OK to ask in here.
Woot! Support answered my ticket, and said to check my rank in game. I'm a Knight now!
So, credit where credit is due: Frontier's support has improved tremendously since the last time I filed a ticket back near release. They got back to me within two days, and took into account the extra comment I'd added to the ticket yesterday about having done a knight level mission and still not progressed.
So if you're stuck they might be able to help. Though obviously I'm hopeful that today's update has fixed this issue.