With a time-dependent event like the anniversary going on, it doesn't do well to have an overflow bag you can't empty that stops you from completing any mission (especially the daily omega stabilization missions).
I keep getting the error that I can't complete the action because the overflow bag has 50 items in it. Problem is it doesn't. It currently holds 19 but I keep getting the error. Last time I checked, 19 was less than 50.
I have discarded items I don't want (but it wasn't 31 of them, so the error still shouldn't have occurred), but I get the error even if I'm just trying to move stuff in my bank to make room for the overflow items. It makes no sense that I can't organize my bank to make room for overflow because there's overflow.
The new (and bugged) overflow system has stopped my being able to play the game at all.
This is my signature. There are many like it, but this one is mine.
0
Comments
4th day waiting on a chair in ESD .. waiting some help, waiting answers to tickets .. and new year event is running :-(
After all, it's not meant to be a permanent storage facility.
An overflow bag should not act like it does now. Let alone potentially cause an item lose (such as mine)
Additionally, donating to fleet after buying from Starbase for that purpose and opening those boxes, was behaving recently in a specific way which we thought was an improvement and now not only it stopped working that way without notice (some of us are having 100/5/5 or close to that doff setup, with multiple bound doffs and sometimes a shortage in mailbox place), it also could have cause some doff loss under some situations which I don't exactly know and don't wish to recreate, and who know what else.
Up to now, notorized to cause issue: possibly doffs (unsure of exact behavior here), prisoners (may be worse), allegedly some (universal or not) console, all could possibly acting as a total block to overflow bag and/or making the char malfunction as if it had reached overflow limit, and who knows maybe other things too.
Additionally I would like to research the faint possible question (or speculation) w/e or not people became possibly limited to the overflow places they had when this patch applied. (I personally cleared all my char's overflow bag before the patch after reading the notes, just in case, this seems to not have helped to say the least or there was other issue, BTW.)
As an added check, if anyone had patience, desire and ability to, I would like to check if lag while doffing and having overflow run from zero to one and then blocked by next, could have also contributed to my doff item loss or was it other factor mentioned possibly as a speculation in my other post in that regard, and also if any items (beside doffs at least) could have been lost due to some new/recurrent nasty overflow bag issue. Note that I couldn't write any bug report however the other post: http://forum.arcgames.com/startrekonline/discussion/comment/13155284/#Comment_13155284 is as close as possible to be such for me.
Yes, most, if not all, of the items in my overflow bag are duplicates of what I already have and, in some cases, are unique items. Therefore I can't take them out of my overflow bag because I already have them. But if the originals are in my bank and I can't take items out of my bank because of the overflow BUG that can't count, then we've hit a stalemate. It's a simple matter of coding somewhere, some algebraic equation that needs revision, whether it is the bag itself or a specific item or type of item or whatever, but that requires a dev to go back into the BUGGED overflow bag rules that they implemented only recently and change it. Question is...will they?
I've tried zoning, logging, etc. and no fix. But I do have other characters that have items in their overflow bag, less than 50, and the overflow BUG doesn't stop them from completing missions, moving items in bank, etc. So far just on my one/main character...which happens to be the one character I'm trying to do the anniversary daily missions on. I can hear the clock just tick-tick-ticking away...
In my case, and I think also in general, it seems to be fixed since the previous maintenance (unscheduled/urgent one instead of the scheduled one)
P.S.
It's rarely said maybe, and I almost forgot, but thank you, I appreciate this fixing