Deployment FAQ

2025
Just a thought - Any chance on getting the list of already-assigned numbers updated so new applications don't waste time requesting numbers that are taken?
Another thought: This deployment page is cross-linked and bookmarked by a lot of people so probably not the best choice to close and replace with new - but maybe delete all the content from 2017-2024 and start fresh at the beginning of the year?

1738048031726.png
 
Last edited:
2025
Just a thought - Any chance on getting the list of already-assigned numbers updated so new applications don't waste time requesting numbers that are taken?
Another thought: This deployment page is cross-linked and bookmarked by a lot of people so probably not the best choice to close and replace with new - but maybe delete all the content from 2017-2024 and start fresh at the beginning of the year?
Seconding this; As a newer member, I'd love if this list can be updated for everyone who has joined since the last update.

No idea what the process is on the backend for staff; if it's a manual process I do not envy who ends up doing it :lol: Wish I could help.

Big thanks if it gets done!
 
I appreciate the detailed break down for deployment! Quick question, Is this updated for 2025? If not, could you tell me where might I find the updated guidelines? Just making sure I follow the correct criteria with the builds. I thought I heard rumors about additional requirements like being active in threads and forums- reaching a specific number of posts with the 405th…
 
I appreciate the detailed break down for deployment! Quick question, Is this updated for 2025? If not, could you tell me where might I find the updated guidelines? Just making sure I follow the correct criteria with the builds. I thought I heard rumors about additional requirements like being active in threads and forums- reaching a specific number of posts with the 405th…
To be clear, Deployment is an entirely optional process that isn’t necessary for participation at events or membership. To deploy, one must be part of their regiment, which you can apply for once you pass your 50 post and 90 day requirements.
 
I appreciate the detailed break down for deployment! Quick question, Is this updated for 2025? If not, could you tell me where might I find the updated guidelines?
I do believe these guidelines are still in effect for 2025. If they are not, someone please correct me.

additional requirements like being active in threads and forums- reaching a specific number of posts with the 405th…
I believe you might be mixing up the Membership requirements with Deployment, however there is some cross-over.

For a person to become a member and consequently join their local regiment, they must have an account over 90 days old, and have made 50 posts/messages. And once you have joined your reg, you can apply for deployment. More info below on Membership.
 
I thought I heard rumors about additional requirements like being active in threads and forums- reaching a specific number of posts with the 405th…
Technically - yes, but in reality those restrictions do not apply to deployments. Those rules apply to being a full member & in kind, a member of a regiment which in and of itself is a requirement for deployment. The guidelines, to my knowledge as a member of 405th staff, have not been changed since the last time the original post in the thread was updated.
 
I appreciate the detailed break down for deployment! Quick question, Is this updated for 2025? If not, could you tell me where might I find the updated guidelines? Just making sure I follow the correct criteria with the builds. I thought I heard rumors about additional requirements like being active in threads and forums- reaching a specific number of posts with the 405th…
These guidelines are still effective and correct for 2025.

As others have explained, you appear to be confusing Deployment with Regiment Membership.

As explained in the the opening of this FAQ, you must be a member of your local Regiment to apply for Deployment, and in order to be a member of your local Regiment, you must have an active account for over 90 days and have made 50 On Topic, Constructive, and Substantial posts. The intent of this guideline is that you make those 50 posts over the course of those 90 days. Behavior like you demonstrated yesterday, making over 20 posts in one day, is not the intent of that guideline. It is really less about the number of posts, even though you have to make a certain number, and more about the content of those posts. The post guideline is there to help demonstrate that you are a constructive, contributing member of the community who has taken the time to gotten to know and engage with the greater community.
 
I have a question regarding tier 3 deployment and custom callsigns:
As far as I'm aware, Halo 3: ODST multiplayer only let's you choose between the skins of only the named characters from the campaign with the exception of being able to adjust colours on some parts of the armour.

Does that mean for a tier 3 deployed ODST suit I would have to have the ROOKIE callsign on my suit if I choose the rookie model (and likewise for BUCK, DARE etc.) Or is there a special exception where, if everything else is matching to a multiplayer armour, I could have my own custom callsign? (In this case it would be CRISPY, and the decal would match the in-game style)

Basically, do I have to be a named character to deploy a tier 3 Halo 3: ODST suit?
 
Does that mean for a tier 3 deployed ODST suit I would have to have the ROOKIE callsign on my suit if I choose the rookie model (and likewise for BUCK, DARE etc.) Or is there a special exception where, if everything else is matching to a multiplayer armour, I could have my own custom callsign? (In this case it would be CRISPY, and the decal would match the in-game style)
Everything else being Tier 3 quality, the use of a member's own last name or callsign or nickname (Within reason, nothing vulgar or blatantly out of Universe like a reference to another fictional property) will not disqualify a member from Tier 3, as the in game armor sets the precedent for both last name with Buck and callsign like Dutch and Romeo, or blank like the Rookie's chest plate in some renders released by Bungie.
 
Everything else being Tier 3 quality, the use of a member's own last name or callsign or nickname (Within reason, nothing vulgar or blatantly out of Universe like a reference to another fictional property) will not disqualify a member from Tier 3, as the in game armor sets the precedent for both last name with Buck and callsign like Dutch and Romeo, or blank like the Rookie's chest plate in some renders released by Bungie.
Thanks for the swift response!
 
2025
Just a thought - Any chance on getting the list of already-assigned numbers updated so new applications don't waste time requesting numbers that are taken?
Another thought: This deployment page is cross-linked and bookmarked by a lot of people so probably not the best choice to close and replace with new - but maybe delete all the content from 2017-2024 and start fresh at the beginning of the year?

Replying to my own post...
Looks like the list on page one was updated 05feb
 
Congratulations on building your first Halo costume! You've taken your first step into a larger world. If you wish to delve deeper into your passion, your next step is the Deployment system.

AugmentedHuman013 and MNKr are the current Division Membership Officers if you have any further questions not covered by this FAQ.

What is Deployment?
Deployment is an optional process where a 405th Regiment Member may voluntarily submit their completed costume for evaluation and sorting into one of three (3) tiers based on the accuracy of their build and it’s fit to the wearer. The program is meant as an acknowledgement and celebration of a member’s hard work on their costume as well as an encouragement and goal for new members starting out on their great journey into the costuming world. Upon successfully completing a Deployment for the first time a member will be issued their Division Identity Number, or DIN, a unique identifier that tracks you through this Program and in the 405th itself.

Do I have to be Deployed to be a member of the 405th?
No. Anyone over the age of 13 is free to create an account and join the 405th forums and make use of all the resources found on 405th.com including The Armory regardless of Regimental affiliation or Deployment status. However, you must be over 18 and a member of your local Regiment to submit a Deployment application.

Do I have to be Deployed to join a Regiment?
No. Anyone who has an account with at least 50 posts who has been on the site for 90 days may request to join their local regiment. A completed costume is not a prerequisite to joining a regiment.

What can a non-deployed member do in a Regiment?
Any Regimental members over the age of 18 may vote in any Regimental election and may be appointed by the Regimental Commanding Officer (RCO) to a Regimental Position such as Regimental Executive Officer (RXO) or Regimental Membership Officer (RMO). Non-Deployed members may attend any event that has not had any limitations placed on it by Division Command, Regimental Command, or the Event Requester.

Are events that Non-Deployed members can’t do?
There has not yet ever been an event that has been limited to "Deployed Members Only," however, because we partner with outside organizations for many of our events, we can not discount the possibility that they will request specific characters, types of costumes, or levels of accuracy for their events. In these instances, Deployment maybe used to select or evaluate those members who will attend that event. However, if no requests or requirements are given by the event organizers, all Deployed and non-Deployed costumes are free to attend the event. The over whelming majority of 405th events, and the default view on events, is that all costumes are welcome.


What are the Tiers for Deployment?
Tier 1 is for those that have successfully completed a Halo Universe costume, but might have inaccuracies or have some fitting errors.
Tier 2 is for those costumes that have achieved a superior level of fit and accuracy, but might still be missing some details.
Tier 3 is for those costumes that have achieved a level of accuracy and fit that they appear to have stepped right out of the game.

Are there different benefits to each Tier?
When it comes to Deployment, a Deployed Member is a Deployed member. Within the 405th, higher level Tier members do not have any special permissions, access, or benefits than a lower Tiered member. All three deployment levels fit into the same membership category, “Deployed Member.” The only time the Tier level might come into consideration is if an outside Event Requester specifically asks for certain costumes or places certain requirements for a High Profile event, but to date, no such event has actually occurred.


What costumes are eligible for Deployment?
There are three main criteria for a deployable costume:

1. Is it a costume from the Official Halo Universe?
In order to be deployed, a costume must be from an official Microsoft or 343i source. While this is primarily the games, Graphic Novels, Live Action Productions, Animated Projects, and even some concept art from Official published Art Books can be considered.

Additionally, the 405th recognizes the partnership with Bungie, and later 343 Industries, that Rooster Teeth’s Red vs Blue series has had. As such, some variants seen in Red vs Blue but not seen in game, such as Insurrectionist ODSTs, Project Freelancer members and other world characters may be considered for Deployment.

Fan art and even art from known Concept Artists that has not been published in an official source or publication is not a basis for deployment. Any concept art must be published by an official source either through Halo media, or on the artists profile on Artstation.

2. Does the costume have a visual reference to be compared to and judged against?
One of the primary aims of Deployment is to celebrate a member’s recreation of a Halo Universe costume. As such, there must be something to compare the finished costume to when determining the accuracy of someone’s build. The visual reference should be of sufficient detail and clarity to accomplish this. This can be achieved via sources such as games, Live action/Animated projects, Graphic novels, and concept art from Novels/Art books.

Additionally, keep in mind that UNSC, Covenant, Forerunner and civilian costumes are eligible for Deployment.

3. Is the costume complete?
In order for a costume to be eligible for Deployment, it must be complete. Partial costumes or costumes missing components or pieces seen in the visual reference will not be considered for Deployment.


That was a lot to read! So... how do I apply for Deployment?
To send in your Deployment Application, go to our "Requests" page:
and click Request Deployment:
Please ensure that all details are filled out, and images are attached. We need full body images of your costume. We cannot accurately inspect your costume if we can't see it! We need images of your costume that show the front, both sides, and the back.

So it's really that simple?
Yes, it is! Please note, that as stated before, Deployment is optional, and will not directly affect your experience with the 405th. MNKr and AugmentedHuman013 are looking forward to helping you progress further with the 405th!

These are examples of the images that should be included in your application:
View attachment 271547View attachment 271548View attachment 271549View attachment 271550
View attachment 367404
View attachment 367405

The Following are General Guidelines, remember that each Costume is graded individually and a Tier Report is generated based on multiple different factors: Fit, Finishing, and Accuracy:

Costume Eligibility:

-Costume must be based on a published, official Halo Universe source, including Games, Comics, Novels, and Art Books so that there is a visual source to objectively compare the finished costume against.
-Costumes based on Concept Art are applicable for Deployment when the designs have been published in an Official Microsoft or 343 Industries publication, such as a “Art of” of book. Designs posted on an individual Artist’s website but not seen in an official publication are not applicable as it can not be verified if the art work is something Bungie or 343i approved of or commissioned or if it is simply "Fan Art" as done by the artist.
-No original, fan designed Armor Sets, permutations, or components are applicable for Deployment.


The Following are general guidelines for each Tier. Each costume will have further specific requirements and items that are looked at and evaluated. Final decisions are up to the discretion of the DMO's


Tier 1 Guidelines:

-Costume must be complete with all primary components present. Any missing primary components will make a costume ineligible for Deployment.
-Complete costumes include paint or finishing work beyond a raw print or raw material.
(Primary components will be determined on a costume by costume basis. An item or component becomes optional for Deployment when in game or in universe references show that an item or component varies in appearance, location, or presence. Examples include pouches or ammo bandoliers on ODSTs or armor/helmet accessories in Halo Reach Armor.)
-Costume may have inaccuracies in color on Under suits, soft goods, and in Armor paint jobs. Under suit colors or Armor paint job may feature colors or patterns not seen In Game.
-Costume details may be “soft” or not well defined. If all armor or Primary Components are physically present, some details maybe missing or omitted for Tier 1.
-“Polygonal” appearance from use of Pepakura may be present. Armor has not been sanded smooth.
-Visible Seams in Foam Armor may be present.
-3D Printed Items may have minimal or no smoothing or sanding done to print lines.
-Armor may lack a Neck Seal for SPARTANS and ODSTs.
-Armor may have fitting or proportion scaling issues. E.G. Slightly over or under sized pieces.
-SPARTAN Armor Under suits or “Tech Suits” may lack details. Under suits may be plain fabric like Underarmor or “Morphsuits.”
-Weathering, including physical damage, black washes, dirt, grime, and exposed silver paint may be either more or less than depicted In Game or in visual references.
-Armor personalization marks or Graffiti may include non-canon references or images, such as references or symbology from other Fictional Universes, e.g. The Overwatch logo or Fallout’s Brotherhood of Steel.


Tier 2 Guidelines:

-If present In-Game, costume must have a Neck Seal, or fabric covering.
-No Manufactures logos are visible on gloves, neck seal/balaclava, or Under suit items.
-Costume may still have inaccuracies in colors or patterns in armor paint schemes, but these items should demonstrate a higher level of fit into the Halo Universe.
-Armored costume under suits will be the correct color or style and be a better match to in game references in material and color selection. For example: SPARTANS will not use camouflage pattern BDUs as their under suit or a white bodysuit in place of a black undersuit.
-Costume may have paint details or decals that simulate armor graffiti or personalization but they must reference items, groups, or historical incidents that exist within the Halo Universe. For example Phrases such as “Remember Reach” or UNSC or ONI related logos or markings. Generic phrases like “Follow Me” or “Come Get Some” and generic logos like the “Skull and Crossbones,” “Smiley Face”, or Animals are acceptable but references to other Fictional Universes are no longer acceptable for Tier 2.
-Halo 4 and 5 tech suits will attempt to visually replicate details.
-Pepakura pieces have had significant smoothing done.
-Foam pieces have had their seams filled.
-3D Printed pieces have had a high level of sanding and smoothing done.
-SPARTAN Armor sets having Handplates will have physical handplates in the correct shape and style. For Tier 2 repainted "Paintball" padded gloves are not acceptable in place of physical hand armor.
-Attachments such as pouches must be close in size and shape to in game references. Lack of accurate attachments would lock the build at Tier 2.


Tier 3 Guidelines:

-Costume must appear to have virtually “Stepped off the screen.”
-Paint Scheme Patterns, Color, and Placement must match references or be able to be replicated in Multiplayer Customization.
-Logos, Symbols, and Personalization appearance and placement must match references or be able to be replicated in Multiplayer Customization. (The 405th Logo or a 405th Regiment Logo in place of an In Game Unit Marker location or Multiplayer Logo/Icon location will be accepted as a special exception.)
- Costume proportions must match In Game appearance and costume must be fitted to the wearer.
-Details must be replicated as close as possible and be present.
-Costumes with Under suit details have had those details recreated either physically by sewing seams in an accurate position, or the use foam, rubber, or leather pieces glued or sewn in place to recreate raised details, or replicate the details by the use of a high quality painted or dye sublimated suit.
-Armor attachment system and any strapping system are not visible.
-Weathering if present in game or in the visual Reference must be replicated in patterns, details, and appearance. For example, A Tier 3 Jorge-052 armor set will have paint chipping, scratches, and visibly weathered armor, whereas a Jorge-052 armor set submitted without any weathering to the armor would be Tier 2.
- “Optional Accessories” like Pouches or ammo bandoliers on characters like ODSTs or Marines that exhibit a variety of placement schemes in Game must be shown to match an in Game reference.
-Individual costumes and costume types will have different Tier 3 Specific Details that must be present. Examples include: “Layered” padding or armor on interior of ODST Thighs, Under suit Details on SPARTAN abdominal areas, neck seals, knee joints, and the Under suit details on Halo 4 and 5 “Tech Suits.”



Special Categories:


“Mash Up” Costumes


-These are Halo costumes “mashed up” with Pop Culture characters. Examples include “Captain America” SPARTANs or “HALO Kitty.”
-Crossover games that make changes or additions to Halo armor such as the Helljumper ODST in Helldivers 2.
-These costumes are only approvable at a Tier 1 Level.
-Popular Culture mash up may be generated by paint scheme or addition of Non-Canon accessories.
-Costume must have a complete Halo Universe costume as a base with all Primary Components of that costume present. For example helmets for Spartan builds instead of out of universe equilvalents such as Stormtrooper helmets.
-Additional details must be cosmetic in applications only, so if they were removed the base costume would still be a Deployable Tier 1 costume. For example a cape on an ODST.


“Mix and Match Armor”

-These are Costumes that mix armor components from across different games or media in a fashion not seen or described in any In-Universe media or references. Examples include Halo 4 armor with Halo Reach Components, such as Halo 4 chest, arm, and leg armor, with a Halo Reach Cod/Posterior armor and Helmet, or use of a Forward Unto Dawn helmet with Halo 3 Mark VI armor.
-These costumes are only approvable at a Tier 1 Level.
-Usage of different armor pieces must be symmetrical, e.g. Both Shins must be from the same game, so as to create a more uniform look.
-Mix of no more than 3 game armor styles.
-Customization available in HALO Infinite through the use of Cross-core customization is not considered Mix and Match so long as it is recreatable in game without the use of glitches.

The Following are the Division Identity Numbers, or DINs, that have been awarded as of [2-4-2025].

Note that the format for the the awarded DIN is "S-[Number.]" We understand that in Canon only SPARTAN-IIs had an operating number of S-[Number], but what you are being awarded through this program is your Division Identity Number, meaning the unique identifier that tracks you through this Program and in the 405th itself. While inspired by the Canon operating number system, it is not an attempt to perfectly recreate it, hence why all 405th members, Spartan, ODST, Marine, AI, and Covenant are given a DIN in the same format.


2 JSnellArt
3 Jocko03
5 James
6 Jai
7 Icon Props
8 Arlock (AZTLAN)
8 Li
9 BlazedStarbon
10 Naomi
11 mawrTRON
11 Leon
13 MyrHerder
15 Ashuraa
15 Kirk
17 SpecOpsSpartan
18 PlanetAlexander
19 Serin
20 DeadpoolXODST (formerly GreY2231)
21 TheSafariMan
23 Daisy
24 SubXzeroXhero
25 Robert
26 Viper 466
28 Saber
29 Joshua
31 Otto
33 EinHander
34 Samuel
37 Alpha (formerly Bucs37DK)
37 Randall
38 thatdamnjodie
39 Isaac
42 Douglas
43 Will
44 Anton
45 ElvenArcane
47 Keiichi
51 Kurt
52 Jorge
53 Margaret
54 JTF4
56 Hibson
58 Linda
59 Malcolm
60 MNKr
62 Maria
63 RandomRanger
64 gliderx64
65 Mebbitts
65 Sheila
66 Soren
68 TurboCharizard
69 Solomon
71 HATE Recon
72 Sylvacan
73 Ulfhedinn073
74 Wayward Flood
75 Cassandra
77 iac300
78 Morkar78
79 Arthur
81 Rene
82 Wendi82
83 TheDarkSpartan
84 Fhajad
87 Kelly
88 CrazedOne1988
90 James
91 vshore100
92 Jerome
93 Grace
96 Musa
97 CrimsonViper97
98 Rock Lobbster
99 August
101 Spurks Donut - formerly Sniper
101 Victor
102 Recon Assassin
103 Ralph
104 Fred
106 NEMES1S
107 Sierra 107
111 Cadet
111 Adriana
112 SSGLordElmo
113 AsgardianHammer
114 BMP Props
116 BrokenHawk
117 John
118 Marinesniper
119 kernelArthritis
120 Mike
121 CasuallyFlacid
122 Joseph
124 Masterchief0624
125 JSLund
126 NegativeCacti
127 KitKatGoose
128 PerniciousDuke
129 Oscar
130 Alice
131 Zylenko
132 ODSTwolf1013
133 Charlie 13
137 Roxas s Embers
139 whereisdanielle
141 Cal
144 Emp Frosty
147 Bowye
149 SigmaProps
153 TillXValhalla
156 Church
158 tennyson
169 Spiderboy196
170 QueenBHartigan
179 Kolala
188 Benton188
194 Smelms
195 CaminusPrime
196 Spiderboy196
198 odstrookie
199 D3LTA
212 Voren Marr
213 BlondieDoes
217 Huntress217
222 GalacticWombat
224 Jerverant formerly Jerryboberri224
226 KaeSpoon
229 SniperWolf
237 CplYapFlip
240 Si3rra 117
246 ScottishLass
247 247District
251 Harri51
257 Schankerz
259 Rickrtickr
264 Shirou
271 PapaBear71
286 brkiker
288 ObiJ3ff
297 Bloxxer
303 mikedem2
311 Evolver79
313 CortexZerks
314 Angus314
317 ixRainShadowxi formerly Raynes Shadow
319 Khan 319
322 InfernalAxe
324 LegacyAlloy227
325 MasterChiefProd
327 Badkitty
328 ArcSol
331 Legend 113
343 Guilty Spark
358 arma358
365 DARKWARRIOR365
366 Electraknite
386 peterthethinker
392 mwmanus
402 SpartanSweed
404 Lukavago
412 GrmblBACHx
416 Jme
418 NewBrody
419 Wicked Demon 15
420 NoviceRobes
422 Oddball422
426 InterfectorF
434 he4thbar
439 CoS Spartan058
445 HeadLocks
450 Dat1Darkrai
474 Kusak3
501 GingerofDoom
504 Optimusaint
505 tahu505
509 FirstPick
511 NobleofDeath16
513 Purichan
518 SparkyRed
526 HotPockets
530 Sean Anwalt
554 Phauxelate
555 B1ondeange1
556 Jobe Devian
564 TrooperJasher
581 581 Erudite Watch
592 FoxODST
593 BeeBoy formerly wilsoncai
613 Augmentedhuman013
615 Deltaraven
621 MicaHusky
626 Wade the Hammer
627 PapaSola
628 Unfit Armory
666 SgtSkittle
698 Off Earth
707 RadMax117
713 CommanderPalmer
717 ScottJackson117 formerly Scott Jackson
728 Skidmorpheus
737 Caboose vs Grif
742 Mullins Props
757 JD of Asgard
770 pipninja
777 Jedi Ranger
795 Sierra Charlie
800 Adam
811 CozmiqVixen
821 LastMinute
829 MrJamin
843 WZProps
871 Thien
894 MDBDesigns
897 Landeros01
919 CherriDragon
921 Sharpfang
922 ZP180
935 Invidiax4fan
953 Shadowpi3
969 ODCA
970 DeltaAlphaZulu
980 Redshirt
985 Serenko3
989 LadyRedCos
999 EndlessForrest
1280 WandererTJ
2424 Dirtdives
3157 JP120800
3330 FANGS
5000 StattingUp
You forgot me T.T
 
Hey - just a thought - Since the website member database seems to be right and include everyone's DIN, even those that are reporting they were left off of the other list(s)...

Maybe you can export the member list to a basic comma separated file and just keep the names and DIN, after importing to your... spreadsheets?

2025-10-02_07-58-12.PNG
 
I believe the discrepency in our files has been corrected. Please limit any conversation in this chat to anyone else who may be missing.
 

Your message may be considered spam for the following reasons:

If you wish to reply despite these issues, check the box below before replying.
Be aware that malicious compliance may result in more severe penalties.
Back
Top