If you look carefully at the video, it looks like he clicks the "yes" but it gets cancelled. Then it doesn't look like it's being clicked when it goes through. Just an observation, not trying to fan any flames.
I only clicked yes with the mouse, I didn't touch enter nor escape. I made sure to record Only clicking Yes (not ok) to use ws, but as you see in the video no ws was used so I lost slots which is not my intention
tfw people get legendary spirit skill because they didn't want to deal with the pop out prompts while ws-ing an item...
Most players that's played long enough learnt it the hard way of wasting one white scroll before always keeping them in the storage until you need to use them. Double clicking the legendary spirit skill to open up the ui is already one extra step of barrier to prevent accidents from happening, as the white scroll tick is shown on the interface. I think a better solution without breaking the game would be to just update the white scroll's item description so that it mentions having it in your inventory while scrolling would mean a potential of it's consumption without proper care. Therefore the player themselves are responsible for any mishaps instead.
TBH this is exactly what it looks like to me lol. Looks like he tried to time the “enter” or “escape” button to line up with his click but messed it up the first time, then got it the second time?? which as we know would result in no WS usage. However the fact that this can happen even with the WS box ticked is pretty annoying, in the context of transparency and UI QOL changes
exactly, this seems like a weird solution and not a QOL change. A fix for a problem (?) which only happened to few players that werent paying enough attention when scrolling with legendary spirit. rollback to previous system, seems unnecessary and makes scrolling with legendary spirit more tedious than it already is (slow process now slower)
My first video I tried to use was shot by phone and very low quality. So I had to attempt it again, and when I finally found a video capture I could use, I made sure it was recording before I clicked yes when the prompt showed up. Make mapleroyals great again!
I've messed up quite a few times trying to do normal scrolling with Legendary Spirit, I knew this was my fault for not unticking the box to use my ws, thus never tried reporting. Also, even if I were to press enter on the keyboard (which i didn't), there was no mention of it not using a white scroll in Matts post. Legendary Spirit will now show a yes/no confirmation prompt when using a White Scroll. Note: At the confirmation prompt; clicking no, pressing escape, or closing your client will proceed with the item scrolling without a White Scroll.
Considering that sometimes when you use the npc chat hotkey to fast track responses it can result in yes or no being selected. Pressing enter probably selects no as the automatic response. However given the nature of how the skill is used, most people would click yes or no instead of pressing a hotkey.
Our? Did you get your item messed up or do you know anyone else that also got their item messed up from the Legendary Spirit skill?
FASTERRR, go try and scroll your first perfect item with a video showing this, if the first slot passed with 10% without using a white scroll, repeat THIS TOP SENTENCE Else, Open a report bug post to ask for refund, indicating the legendary spirit skill is not working as intended. RMB TO SHOW UR WS IN INVENTORY and CLICKING YES Thank me later
Any updates?? I want my 9b claw back and I won't use the skill anymore until it's fixed You guys refund for people who "lose" or drop their items. I wanna scroll stuff like i always have (before this update)... If it was my mistake I wouldn't have bothered making a post.
It would be interesting to know what the technical explanation would be for a bug like this since 2 users had different results after both clicked 'Yes' in the prompt. I think it's unlikely that the client would send a 'Yes' for one and a 'No' for the other to the server, but it's either that OR there's an unknown bug in the WS code.
