I probably wouldn't be a good "lead" for the team, I was just shouting out ideas lolOriginally Posted by English Mobster
You'd really need an actual team for stuff like this (yes, I'm captain obvious). Unlike Sapien, it's cooperative (both game wise and communication wise). So you can have all of your team in game doing their parts. You'd have maybe two or three geometry guys working on an agreed layout or just messing around. As they mass out respected parts of the level you then have populators start fielding the world with weapons and decorators. Then you have the game type people come in and populate the currently loaded game type's data (spawn points, objectives, etc). You can also have people in testing things while parts are still being worked on. They can make sure objects are completely aligned, or that one weapon doesn't favor one side, etc. It's a very multithreaded process, everyone can be doing their part at almost the exact same time, and communicate in real time.
Because of that, old habits and ideas used in HaloCE map making don't really apply or need to be reworked to fit in. The "team" would now become a squad, with multiple teams of people underneath it. Each team would be working on a different map. Like say, due to the networked ability of Forge, you can now have 5 people doing the same work at the same time as just one.
This enables you to truly start to compartmentalize your work force. Think of it as the the "hyperthreading" age of map making. We use to run on single cores (one person working in one editor) but now we have multiple cores (multiple people working in the same editor).
You wouldn't want to advertise until you have something solid. That is, known squad\team members and their responsibilities in their respected departments.
E: the team could also go by HEK: Halo Editing Kids. You know, only add more ambiguity to Halo acronyms like Custom Edition did lol.
Bookmarks