[The Character Simulator]
I hope this is being put in the right place. I don't typically use the forums, but I know that most of Mabi's player base loves fashion, & very likely use
this character simulator to plan outfits or make characters. It is personally my favorite site to use when I get an outfit idea, & I want to mess around with the colors before solidifying them in-game.
The character simulator doesn't have all the outfits, but it does have a good portion of them. The only problem? Most of the newer outfits are in the untranslated Korean section of the lists, & unless you speak/read Korean or want to painstakingly click through each outfit until you find the one you're looking for, it can be difficult when you just wanted to make a character using X outfit, or figure out if you're putting that dye on part A -F, ect.
Before I continue, I want to establish: this is in no way to bash the creator(s) of the simulator, I don't know them personally, they could be super busy & don't have time to translate, they could just not enjoy translating to begin with & decided they just want to stick with Korean, heck they could be waiting till eternity to update the site before translating everything. I have no clue, but whatever reason it is understandable. But still leaves us non-Korean speaking fashionogi-ers with the issue.
Well, as the title suggests, I did it. I went through the Korean section of the lists, and I made
a helpful google sheet so fellow fashionogi peeps can find their outfits with
less hassle. It is in alphabetical order to start with, but you can also use ctrl+f to open a search box, if you know what outfit you're looking for.
[Important Things to Note]
1.) This is not
all the outfits, but I specifically chose ones that I felt were highly popular, which ended up being most of them. If an outfit you're looking for isn't on this list, I will take requests to look for it & add it to the list, but please remember that not every outfit is on the simulator, so even if I look for it, It may not be there.
2.) If
you find an outfit on there that isn't on the list, & you want me to add it, you can simply send me a screenshot of the outfit & it's name in the simulator (with the English name if you know it) & I will add it.
3.) For the "Male/Unisex Variant" & "Female Variant" columns: If one box is filled but not the other, it is either a.) only for either male or female, or b.) the Korean name for the outfit is the exact same, so both versions will come up if you search it.
4.) Piggybacking off that last one: If you are new to this simulator, any male only items are highlighted blue, unisex is white, & female is pink. So if you search an item both genders share a name in Korean, just click the one that corresponds with the color of the gender you're looking for.
5.) There was an oversight on my part, that I didn't realize till I was about 150 items in: I did all this in the 'Armor' section of the list, which means if you want to look for hats/gloves/shoes/ect from any given set, you have to
delete the last word or two from the name, as this word is usually "outfit/wear/garment/uniform/ect." this is something I will fix eventually, but this all took me 10+ hours to do, & atm I just want to go to bed.
6.) Some outfits were not fully named, as in I didn't write out the whole outfit's name. I mainly removed the words "suit/dress/outfit/wear" from most of the names, as I figured most people when searching for an outfit, would use the first 2-3 words of it's name, to try to locate them. As such: you should still be able to find everything fine, I didn't remove anything vital to my knowledge. NPC outfits in particular I admittedly got really lazy with (& will also fix later) & for most of them I
just used their names. So searching things like "Morfyd/Etain/Piran" should still come up with their outfits, but the English part of the list is
just their names. Sorry.
7.) There are also some outfits (not a lot) that I knew were parts of the same 'set' but were named differently (E.I: Beast Suit & Beauty Dress ect) which I put in the same box, this is another thing I am aware I did pretty inefficiently, & is again another thing I will fix in the future.
