Welcome to Open Carnage

A resource for Halo 1 modding and tech, with unique means of rewarding individual content creation and support. Have a wander to see why we're worth the time! EST. 2012


  • Content count

  • Joined

  • Last visited

  • Raffle Tickets



About gbMichelle

  • Birthday March 10

Extra Information

  • Gender
  • Occupation
    The right side of the bed
  • Raffle Victor
  • Outstanding Mapper

Contact Methods

Computer Details

  • Name
  • Central Processor
    AMD FX-6300 "Vishera" 3.5GHz 6-Core cooled with a Hyper 212 EVO
  • Motherboard
    ASRock 970 PRO3 R2.0
  • Graphics
    GTX 1060
  • Memory
    16GB DDR3-1600
  • Storage
    ~2TB all in SSDs
  • Power Supply
    Sharkoon WPM600
  • Case
    Aerocool V3X Black Edition (The internal layout is awful)
  • Display
    2x1080p 16:9 + 1x1024p 4:3
  • Keyboard
    Cherry G84-4100
  • Mouse
    Trust GXT 177
  • Operating System

Recent Profile Visitors

2,923 profile views
  1. The tracking camera is relative. 0 0 0 is used as a reference point. Make sure that your camera point for the tracking shot is positioned pointing at 0 0 0 in the map. Use spacebar to place a marker at your screen position.
  2. Mozz Editing Kit The MEK is a powerful easy to use set of powerful tools that can be used to mod Halo 1 and other games based on the blam! engine. It is fully Windows and Linux compatible. It comes with: Mozzarilla Mozzarilla is a replacement for Guerilla, it has support for multiple tags directories, exporting single tag blocks, more comment boxes explaining how things work and many tools. Like: a model compiler, physics compiler, animation compiler, animation decompressor, an option to import bitmaps directly from DDS, a batch bitmap converter/optimizer, bitmap source extractor, sound compiler (currently only Xbox ADPCM and 16bit PCM), tag directory error locator, string list and hud message compilers, converters that allow you to convert basically any type of model to a gbx model, or any object type to any other object type. It supports Vanilla, Opensauce, Stubbs the Zombie, and (Expirimental) Halo 3 tags. It also supports some Misc Halo file types like gametypes. It also has highly customizable themes (styles) and settings that allow you to choose exactly how you want to use the tool. Refinery Refinery is a tool for extracting tag data from maps, but also for viewing tag data in map files. It supports extracting tags from Vanilla Halo 1 PC, Custom Edition, Xbox, Demo. But also from OpenSauce and vap maps. Halo 2 is partially supported, and Halo 3 Xbox 360 maps have experimental support. If a map you want to rip is protected then have no fear! Refinery comes with a powerful deprotection option that can intelligently name tags and repair classes based on many heuristics found inside of the map. It also has a data extraction mode. The data extraction mode instead of extracting tags will extract bitmaps, models, animations, scripts. This is really useful if you for instance want to use assets from a map in something other than Halo CE. Pool Pool is a program made to help people who aren't super familiar with tool or command line applications. It comes with explanations for all commands, helpful templates, and options to for instance run batch jobs, or multiple simultaneous jobs. It also comes with various patches that you can apply to your tool.exe to for instance remove the map file size limit, increase the vertex and index buffer size, and a multi-language compatible resource maps fix. But that's not all... The MEK also comes with a plethora of 3DS Max scripts that are useful for 3D creation with the Halo engine. And there are more tools being worked on that fill different gaps in the open source Halo 1 modding kit. Ones that I am very excited to show you once they're ready. How do I install the MEK? There is a few ways to do this. But right now the best way is to get either the MEK or MEKE. MEKE (The easier to install windows-only version) Keep in mind that this version currently updates less frequently. 1. Get the MEK_Essentials_Setup.exe Get it from here from here: [MEK Releases] 2. Run the installer (lol) MEK (Python version, most up-to-date version) Installing the Python version of the MEK is actually pretty easy. 1. Get Python from your favorite source. if you are on Windows I highly suggest getting it from the Windows store [link]. The Windows Store version is nice because it automatically installs the right version (64-bit) and you don't need to do anything but just click the button. Don't worry, you won't need to log into the store. 2. Get the MEK_Installer_Python.zip Get it from here from here: [MEK Releases] 3. Run the MEK Installer Now watch out, wherever you put your MEK installer is where the MEK will install, UNLESS you pick an installation directory using the "Browse" option 4. Click install and wait until it is done After this you are basically set, the files to run the MEK should have appeared in the current folder or whatever folder you chose to install to. Be sure to frequently run your MEK_Installer.py to check for updates. Credits (This section is probably very incomplete) Direct contributors @Moses_of_Egypt @gbMichelle Mimickal Other sources of information @Kavawuvi @Sparky Opensauce Frequent testers @Kavawuvi @Vaporeon @MrChromed @Masterz1337 CMT @Jesse @SOI_7 Whix Where can I in real time discuss these tools and how to use them? You can do so in the CE Reclaimers Discord Server [link] Of course this thread is also a good place to discuss the tools, but keep in mind that the Discord is more frequently checked. How can I contribute? You can find the sources at our GitHub organization, Sigmmma! [link] You can also report bugs on the GitHub repositories' issue pages, here, or in the Discord server. [link] You can also tell us what you'd like to see added, or what kind of tools you'd like to see in the future. Most of the libraries and programs in the MEK are licensed under the GNU General Public License v3.0. [link] Shout out to invader, another Opensource toolkit made by people who frequently help us out. [link]
  3. I guess it also makes sense to link to the github. Since it's open source and licensed under GPLv3 https://github.com/XboxChaos/Assembly
  4. Can't detect it because that info is never sent to the server as it's irrelevant to the netcode.
  5. Honestly? Tough shit imo.
  6. If you used a better compression scheme that looked better that would also not save in the tag. If you can recreate what you made with your tools using vanilla tool, what is the point of your tool? To be clear, compatibility with legacy is good, but I don't think we should be limiting ourselves to that all the time. The whole draw for this project for me is to be able to do stuff that I've been manually purposefully avoiding tool to accomplish, but automated. Edit: Even if it means adding an extra switch to my command.
  7. At least with this one you could allow for a switch that lets you use sizes bigger than this
  8. This project frustrates me, because every time something new cool and useful is added it just gets removed. :/
  9. Add this to your sapp init. And use the latest build in this zip. auto_update 0 Halo CE SAPP 9.X.7z
  10. Are you using sapp? If so, then sapp owned your install by updating to it's 10.x version and broke. You'd need to stick with a 9.x version and disable updates.
  11. Please create a windows version. HaloSpriteDoer breaks alphas/transparency. I also want to only have to document the usage for one tool
  12. This new tool will be better once binaries are released.
  13. I know right? The last few years have been moving fast.
  14. Yeah, it's true, HEK+ is old and bad. Luckily a lot of us were able to come together and make a worthy replacement with Refinery.
  15. Maybe you can use the RSS feeds on this site to spam the CE3 inbox so you will always be sure that you have everything for a HMU.