Hey,
1)Red-hooded Paladin is a skin that is only used in the story. Once you unlock it as a class, you only get the blue-hooded skin.
2)You can get Tasty Treats from the latest banners, they replace common gifts.
3)Yeah, you're right, I'll look into it.
Hey, just saw your bug report comment.
It is incredibly detailed, thank you so much for the feedback!
But one of the bugs there is game-breaking, I'd prefer to keep it from leaking to the public.
I'm replying to this comment, hoping that you'll see the notification anyway.
1)About the Miyabi bug. That's probably a combination of different things. What's her gear, and who is in your party?
2)So about the going out-of-bounds bug. This bug was fixed in patch (f). And the version uploaded here is (h). What's your game version? You can check it in the main menu.
3)About the paladin skin. His color scheme is tied to the story, and because he is in a lot of heavily scripted cutscenes - it would be pretty time consuming to add something like that.
4)And about the explicit stats... A new crafting system will be added very soon. :)
Ahh I'm sorry xd but I figured you guys would do that because this bug is really game-breaking, and yeah, you're right, I didn't notice you updated it (I'm using 1.11D), I'm updating it right now
The set I use for Mayabi
If it helps I can try to redo the bug so I can screen record it and share it via link, but it happens after I go several runs with her on my team. (I noticed I had deactivated accidentally TIER II Moon's Grave, maybe that was causing it?)
About the skin, I imagine how much work and time it would take, but who knows in the future? :p
I remembered, could it really be the sword? I remember that when this bug happened, I loaded old saves and it still continued, so I had the idea to unequip all the equipment from Mayabi, cuz it happened 2 hours after I added her to my team, I tried to remove all equips including the sword and the bug still going on, or I had to find a auto save that the bug didn't happen yet or remove her from the team in any save(including the most recent) and the bug was resolved.
I apologize if this wasn't very helpful, and I only wasted your time. As I said, I didn't read the changelog; this bug happened almost two months ago (version 1.10) I was very busy before, and at the time I didn't come up with the idea to record it or make a copy of the save. If any bug ever happen again I'm going to record it immediately and show every possible detail, but before reporting I'll check if I'm using the lastest version :3