We have located an issue in the mining system that sometimes prevents claimed resources from being completely excavated.
The issue causes the miner to get an internal error when he/she is excavating a resource which prevents a complete excavation of the resource site. We can assure you that we are giving this issue top priority and hope to have it fixed soon. Please stay tuned to this section for any further information regarding this matter.
For those who are affected by this issue, please proceed as follows:
Contact support by filing a support case.
Also, send a screenshot of the deposit site that verifies that the error occurred. Press default key āUā to get the time and position of the incident.
Those of you who have already contacted support regarding this matter do NOT need to send a new support case. All your reports have been registered and we will get back to you once we have more information.
We sincerely apologize for any inconvenience caused.
September? They are finishing their vacation early this year?
I wonder what happens to those who donāt have a screen shot programā¦ ok, they have Print screen button, and can alt del out of entropia (if that still works) or run in window mode, but it seems the onus (spelling?) is on the customer to report an MA error, rather than MA automatically rectifying it based on their logsā¦ Surely it cant be that hard to run a search for all claims not fully mined - canāt think of another reason why a resourse wouldnt be fully minedā¦
How about fixing that āissueā that causes us all to have a 20% return in mining, crafting and hunting and give us something we can sustain ourselves on!!!:rolleyes:
I was the first player to experience the previous occurrence of this bug back in May (just before Joe Jeff).
The first occurrence reported on this Forum was on a Saturday morning (by me), and there were about 6 further reports over the next week. MA eventually refunded at least those players who reported the error on this Forum.
After a week there were no more reported occurrences, so I deduced someone at MA had released bugged code, and then fixed it, though MA never made any public announcement.
Now it seems the bug is back, and MA have learnt from the earlier criticisms by making this announcement. But it looks like the original bugged code was merely regressed without the bug being understood, and now the same bugged code has been re-released.
I stopped mining for two weeks whilst the earlier bug was being investigated and until I was compensated because I didnāt trust the mining system, so I donāt think MA had any choice now except to guarantee refunds to anyone who might be affected this time.
As it happens I was fortunate to get a Vast this afternoon, which I extracted without problem, but I would have been just as annoyed as those who have been affected now if I hadnāt been able to.
Oh this may put a bomb under plans starting this friday.
Is this bug a regular occuring bug or something that just occurs here and there ? Is it generally with larger finds or smaller finds ? Is it limited to any particular location, or is universe wide ?
no criteria. I had it on a small belkar, i saw other on substantial lyst etc.
Actually it is impossible. Because once the claim expires, it might get an extra 24 hours time life, but at some point it will expire. Since that moment the system sees it as extracted. And tbh I doubt they have such item as āclaim not fully minedā, it would only add unnecessary workflow load.
I had a vast of lyst that i could extract 2/3 of it.
I extracted part by part with breaks.
It broke in the middle of extracting session, after I made Alt-Tab.
I 've sent support case with details and screenshots 3-4 weeks ago.
Good to see its not forgotten :yay:
NICE MA for letting ppl know, this rocks!!! :yay: Took a bit of time since I think this was first reported after the VU? :scratch2: Wondering if thereās anything we could have done to help you find and identify it faster?
Now, just hope youāre not too flooded with fake screenshots. I hope ppl realize that MA has the ability to check the time, date , inventory etc against them. :wise:
In May, I and the others were refunded the exact amount of Ore we had not extracted. In my case this was 2 weeks after I logged my case, and 10 days after the claim expired. So I would say that, yes, MA can get this information from their log files.
We submitted screen prints, but I think this was merely to get MA to look at the Support case seriously (actually in May they didnāt for a while), and I was even asked for a Dxdiag print, which was clearly just a formality and could not have helped with diagnosing the bug.
I would hope that MA would refund anyone who submits a support case, so long as MAās logs confirm the problem, because it may be too late or impossible to take a screen shot if the claim deed has expired.
