We are happy to announce that reimbursement has been completed for all those who lost skillpoints due to the inadvertent pausing of skill queues that occurred on June 9th.
Skillpoints have been reimbursed at the standard rate of 40 skillpoints for every minute that affected players had their skill queues paused by the script that was ran on June 8th.
If for any reason you were affected by this issue and have not been reimbursed by the deployment today, please feel free to contact our customer support team by filing a support ticket via the Help Center, and our friendly Game Masters will be more than happy to assist.
Please feel free to discuss in this thread.
UPDATE - 26/06/2017:
We’re aware that a large proportion of the reimbursements didn’t take place today as planned, and are looking to complete these over the course of the next 48 hours or so.**
Apologies for the delay in getting the skillpoints back to you guys, we hope to have this resolved very soon.
UPDATE - 29/06/2017:
All reimbursements of missing skillpoints have now been completed. Please be aware of the following reimbursement criteria:
Skillpoints have only been reimbursed for the time that skill queues were paused. If your skill queue was only paused for two minutes, then you will have only received an 80 skillpoint reimbursement. This is not a blanket SP reimbursement of a standard amount, it is tailored to the number of skillpoints lost on a USER level.
Gaps in training for all characters on an account were taken into consideration for this reimbursement, which means if you lost two minutes training on one character, and one minute training on another, you will have been reimbursed three minutes worth of skill training, which equates to 120 skillpoints.
Because of the nature of the issue, if you had MCT activated, then all of the skillpoints reimbursed will have been reimbursed to the character on the account which has the most skillpoints, regardless of which training queue they were lost from.
Our Customer Support Team are currently working through the tickets that are in our system related to this right now, and we’ll get to everyone who has a ticket filed with us as soon as possible.