How do YOU organize your blueprints?

I use alot of very similar builds with slight differences…mostly a module or a different cab on the same general build…maybe a co-driver change etc…

I like to try out various strats and stats…never really sold on just one iteration of a build…just to shake things up ya know…

So…i was curious how YOU ALL organize your blueprints. Its easy for me to get mine mixed up because there are a lot similar so i usually label mine by Wep/Cab/module difference…or something like that.

What does your blueprint label/system look like? Heres mine…






If I’m working a new build, I just temporaily call it “New” until it’s done. A quarter of my builds have descriptive names, like “Lo PS SG”, which is a low-powerscore shotgun build, or “AC Maniac 50” which uses AC50 autocannons, as compared to my “AC Maniac 72” which uses AC 72s.

Most of my cars have strange names. Many of them are anthropromorphic and sport names like “The Wierdo”, “The Zorbus”, “The Glom” and “Snorkus”, just to name a few. “Fire Bug” is a copter with the face of a gnat and uses incinerators. “Mortimer” is a walking mouse with Corvos in his hands. “Lord of Roaches” looks just like that with a Morta for mandibles. “Slice and Dice” has a sorta-human faces and has Harvesters for teeth. “Firefly” is a walking lightning bug whose abdomen actually lights up, and periodically releases 2 baby fire flies (Fatums) . “Electric Storm” is a cloud-shaped copter painted to resemble an ominous lightning storm spirit, and packs three Sparks.

1 Like

I like your idea of individual unique names… i wish i could do that but i have like 11 very close fatum builds so the name uniqueness kind of gets lost when dealing with so many similar builds that look the same. Thanks for sharing.

No organization, total chaos

2 Likes

I base it off what the build does.

Examples:
“Reaper_Booster” : 2000 km/h speedy heli, uses reaper recoil as boost.
“Heavy_Quadcopter” : my most durable heli, which has 4 maple rotors (and a tail rotor).
“Fast_Avalanche” : my speedy avalanche build for shooting and running away to reload to shoot again later.

Sometimes if there are multiple versions of a build, I duplicate it, test it, and delete the lesser version. I keep the same name for my builds by doing this.

If I want the same name, but made a completely different build (Like when I rebuild and idea from scratch), I add “_V#” where #= the number of times I rebuilt that idea from scratch.

Example:
“Plane_V3” : The 3rd plane I’ve made, which looks completely different from “Plane” and “Plane_V2”

This also helps me name my ranges on exhibition:

Examples:
“Bouncy_House_V9” : A concrete box with jumper pads to bounce in. Not the same as the previous versions.
“Pin_Thrower_V6” : This one is kind of an anomaly, It was the same as the previous ones just a lot bigger. V6 is the last one, because of range point limit, and I was unable to make it any bigger.

The way I USED to do it was “Vehicle_#” where #= the build number. This was fine at first when all my builds were the same, but when I started making different builds entirely (with different cabin/guns/modules/etc.) it got a bit confusing. I still use this method, but only on leviathans, which I haven’t build a new leviathan in a while. I think the last one I made was “Vehicle_59” a long time ago.

1 Like