Macross 30... Working on Translation Guide in Games Posted April 25, 2017 It's been a while since I've messed with blueprints so my memory may be off, but if I remember correctly the idea is to use the *most* parts possible, and save the high-value parts for blueprints with higher thresholds. Use as many low-value parts as possible, so that you'll still have the higher-value parts when you need them. --- I feel like I should touch on this here as I've gotten some emails about it, and maybe I should add it to the FAQ section of the guide, but re: translating the M30 game script... I have, in fact, looked into doing that. Personally I don't think it's very feasible. Someone did rip the script of the game, which theoretically makes a translation effort much easier... BUT the actual word file has a lot of programming goblety-gook that has to be sorted through to find the actual lines of dialog. For every one character used in dialog, there are three or four random characters/symbols, and there's no clear demarcation between the two. Furthermore, much of the script (at least in the early chapters) is super-boring, gamey stuff. (Basically a lot of tutorialization and basic setting explanation that is profoundly tedious to translate). I believe there are some bilingual Lets Players who tackled M30, who explain/translate as they play. I'm not very familiar with them, but if you want a better understanding of the story that might be the best approach to take.