Enclusion

What a shitshow... there's no way to tell this story without giving a lot of credit to whoever began DDoSing the forum back in April of '22, but that was only the beginning of the drama that got us to this point. I unfortunately wasn't able to speak candidly about most of the events since the beginning of the attacks, but that's no longer an issue, so this thread will serve as the explainer.
 
For those that don't want to read the drama dump that follows, the short of our current status is that the site is back and there are no plans to abandon it. However given the decline of forums in general, and due to the loss of trust that inevitably followed the long period of outage, loss of community data, and lack of transparency provided by myself, Open Carnage is not returning as a "live" site. OC is in a read-only state for the most part. For the next few months or so, existing members can edit their content if they wish to provide any updates that were lost. Anything on OC after April 18th of 2022 is otherwise gone.
 

Discord Server
Our Discord server has never been known for its modding discussions. It's served as a general chatroom for the long-time members of the OC community, and made it easy for anyone to keep up to date on new community content. That latter utility is effectively gone with the closing of the forum, and just about any subject for a Discord server can still keep friends together. So what's next? I don't know, but we'll probably try doing something new with it. I'll talk with you guys there!

Gun Game (v1.7)
 
A simple progression based game inspired by COD's Gun Game.
Every kill rewards the player with a new weapon. The first player to reach the last weapon with 10 kills wins.
 
[!] Note: 
This script is designed for maps with stock tags.
 
 
See this game in action:
IP: jericraft.net.nz:2309
Server name: Little NZ #2 | Gun Game
 
Gun Game.lua

@Iggy's donated his raffle winnings this month; thank you!

Updated with a couple of bug fixes:
 
1. Perk commands fixed.
2. You can no longer buy perks while dead.
 
~edit
Bug fix, money now saves to accounts.json correctly

First update since the new place:
 
 

Your work creating Chimera is one of the main reasons I came back to playing Halo, it improves the experience so much. Thank you.

Your work creating Chimera is one of the main reasons I came back to playing Halo, it improves the experience so much. Thank you.

My brother got a short clip of me trying to break through this frozen dirt
 
 
 

I'm not making much progress today either
 
 

Your work creating Chimera is one of the main reasons I came back to playing Halo, it improves the experience so much. Thank you.

Your work creating Chimera is one of the main reasons I came back to playing Halo, it improves the experience so much. Thank you.

Added a second version of this script that doesn't involve stats saving. Balances are reset at the beginning of each game.
See OP for links.

Big change to the script.
I never really liked binding accounts to the IP, as a player will lose their stats when it changes or if the server is restarted. 
As such, I have written an account saving system for the Market script.

Players are now required to create an account (in-game) to use it.
 
Account Management Commands:
1. /account create <username> <password>
You'll be logged in automatically after account creation.
 
2. /account login <username> <password>

Account details are saved to a local database called accounts.json.
Some data is cached for a period of time, based on your IP address.
If your IP changes or the server is restarted, you will have to log in again.
 
Also added two new features: Flashlight teleporting and command cooldowns. 
1. If you have enough money, press your flashlight key to teleport to wherever you're aiming.
2. All commands (including flashlight boosting) have configurable cooldowns (default 60 seconds each).
 
Technical note about the Market script and data caching:
When you log in with the correct username and password, your balance will be restored. 

Balances are linked to a JSON table and the table is saved to the file when the game ends.
You do not need to be online when your stats are saved during end-game. This is due to them being cached for a period of time, based on your IP address. So long as the game ends within a reasonable amount of time, and not so long that dynamic IP addresses have a chance to change; I'm talking like, 24 hours or so. Most games end within 20 minutes.
 
That database looks like this, by the way:
{   "Player1": {     "balance": 1000,     "password": "password1234"   },   "Player2": {     "balance": 500,     "password": "12345"   } }  
Alternatively, I could save a player's stats to the JSON database every time their balance is updated.
But that would be too many i/o operations and might cause lag (especially on larger databases); This is why I opted to save stats when the game ends.
The key of the account table is their custom username, by the way. Not gamer tag.
 
Video demonstration of this system:
 
 

I'd say it's my software. Chimera is definitely on the top, fixing a number of issues that not even HAC2 would fix and ultimately turning Halo PC into a proper PC game with its high quality widescreen hack and interpolation.
To a lesser extent, Invader which has been picking up some traction likely thanks to MCC. I've spent so long on this one.
But even Deathstar was an old tool I made that people used as it provided the best-in-class deprotection at the time.
 

Speaking of @Sceny, Dynamic Fire should probably be on my list too lol

The only noteworthy things I can come up with that actually got released/uploaded:
 
 

Crazy to think that you're 2 of those 25 views. I can't wait to see what other quality stuff others post.

I remember that video, way back!

All of my work is lost to time but remember when we used to use patching software because map files were too large to upload and download? I uploaded to Modhalo a patch of a logmodded bloodgulch trial map mostly as a meme but it got rave reviews. From that experience I learned that you don't need to have custom assets and flashy junk, you just need to think very carefully about the sandbox you're creating.
 
It's interesting you post this topic because I recently discovered some old videos on my old youtube account that I forgot I had. There is one video that is the only evidence of my extensive work with particle effects, and the only thing it shows is an early test of a single explosion on a single material. I was very proud of the effects that I made and I was getting close to a release but it was all lost before release in spring 2011. Garbage tags are extremely under-utilized by the modding community, even to this day. Using carefully crafted garbage tag models you can work around the particle effect limits and add a real richness to Halo's effects.
 
 

What are the things you've built for Halo that you're most proud of, or are best known for?
 
For me, probably:
 

Download Mega: https://mega.nz/file/Fl1kRaSC#ePso1q5txFoaedlyfb3txw6cO2bElWG9eQiQ2LRYHQY
 
Download Nexus: https://www.nexusmods.com/halothemasterchiefcollection/mods/1739
 
Optional UI Files: https://mega.nz/file/Vg90TYYa#si7oSijEOJ1mUwwbl1Ypgy74voWqUiXbt2YutaEGmt4
 
Conflux is a symmetrical competitive map set in a Forerunner facility on the edge of a cliff. It was designed with a "tug of war" style of flow, where team positioning and careful movement through the center are emphasized.

Teams start the match facing the center platform in the main atrium, with the base of a large beam emitter blocking the line of sight from spawn to spawn. Each team spawn has a large doorway in the middle, with a direct line of sight from the center platform. Walking through this doorway will lead you to a deployable Grav Lift, followed by a one-way drop-down to the center floor. From here, players can move to take the Overshield or move to the gold lift that will take them up to a raised platform that overlooks the center platform.

Each team's base has one middle room flanked by an elevated room that grants them access to the center platform and a lower room that will lead them to the gold lift. Each team will find a Sniper Rifle in this lower room. Looking towards the back of the lower room, players will find a doorway leading to another room with a long, "elbow" shaped ramp leading them up to a bridge that will take them back to their spawn or to a hallway that leads to the top of the gold lift.

Players that move to the elevated room in their base will find a small platform that overlooks their side of the central atrium, which they can also use to jump to the center platform. In this same area, players will another overlook that has dominance over an overhang on the cliffside that runs the length of the map. At the center of this location is a man cannon that players can use to launch themselves to the center platform. The Overshield spawns just in front of the man cannon.

The map is designed primarily for CTF and Slayer, although it supports all of the default Halo 3 gametypes.

The weapon and equipment set on the map include the following:
3 Battle Rifles per side.
2 Assault Rifles per side.
2 Brute Plasma Rifles per side.
2 SMGs per side.
1 Auto Mag per side.
1 Sniper Rifle per side.
1 Deployable Grav Lift per side.
1 Sentinel Beam under the center platform.
1 Gravity Hammer on the center platform.
1 Power Drain at the gold lift.
1 Bubble Shield at the man cannon.
1 Overshield between the man cannon and the center platform.

How to install and play:
-Navigate to the install location of Halo: The Master Chief Collection
-Go to the Halo 3 folder, and then the maps folder
-Backup the file called docks.map by either renaming it, or moving it to another folder
-Drag the new docks.map file into the maps folder
-Select the map Longshore in Custom Games or Forge to play

Thanks! Making it look like a Bungie map was the goal haha.

Updated with further improvements and a new feature:
 
Chat integration whitelisting.
* If you don't have the role defined in the whitelist.role property of settings.lua then you will not be able to send messages to Halo. 
 

~ edit (17/02/22 @ 10:44 AM NZST)
Change Log:

1. Small bug fix for embedded status messages.
2. Updated the OP as well as the GitHub release page.
 
~ edit (18/02/22 @ 15:43 PM NZST)
Change Log:
1. Another small bug fix for embedded status messages.

Amazing! I am so glad this place exists.