got 100 splinters, how do i "create" a breachstone
once again, this game leaves you with NO FUCKING IDEA on what to do
tried vendoring them. Offer wisdom scroll frags. NO thanks!! tried putting them in map device. NOPE!! Oh jeez, I just tried this....unstack1 of them, recombine, then *poof* breachstone appears. SOOOOOOOOOO fucking stupid btw, can I please have my signed atlas map now? It's been almost 4 months......wtf Last bumped on Dec 23, 2016, 5:40:11 PM
|
![]() |
It's because they can't combine in the currency tab and don't try to combine unless more splinters are addressed.
|
![]() |
contact support (nicely) about your map.
|
![]() |
Move 100 to your bag, break the stack of 100 into 2 stacks, then re-stack then into a pile of 100, and they will transform then. As already mentioned, they wont combine in the currency tab.
Had to google this myself the other week. |
![]() |
yeah, they are broken, if they are in your inventory they are fine, but in the bank or currency area - broken.
I can't believe this is still broken, you would think one of the main mechanics of this league would be fixed the day it was found to be broken - but 2 weeks later... nothing. |
![]() |
just googled this, also had no idea
|
![]() |
" broken? how do you think the issue should have been implemented? age and treachery will triumph over youth and skill!
| |
" Not broken i guess? Why do you think there are 100 threads with this same issue. People wanna get their breachstones. |
![]() |
" so, how would you have implemented it? age and treachery will triumph over youth and skill!
| |
I mean, to be fair it does kind of make sense for them to not automatically combine in a currency tab. You have limited 'wild card' currency slots - in fact just enough for the 5 types of splinters - so I would in fact be kind of annoyed if I had to use 2 spots for a single type of splinter/breachstone when I could just store splinters up to 5000 or whatever and easily combine them when I want to run the area.
Obviously, the issue here is that it's very confusing and not obvious that it works this way, but I wouldn't call it a bug so much as a design choice. |
![]() |