misterjesus (npub1mw4…p6t6) :back_from_gab: :musashi_berseker: :abigail_williams: :musashi: :benienma: :astolfo: :chloe: 🏆🏆 winner of the Holy Gab War and Holy Poast War (npub172u…2cl7) (npub17jx…w2x2) Doc Scranton (npub13uw…shsz) >I am a dumbass regular business apps developer, and I've managed to fix compile issues between Linux and Windows on a C++ project. I would imagine a professional games programmer could do this with ease.
Here's where they fucked up. What happened was 343 wanted to keep all 4 games on the same UI with one main launcher for all 4, as opposed to having a single launcher load each game up and then handle MP/SP.
I am not sure what the reasoning for this, but I suspect it was due to population count worries. This is why Halo CEA did not have MP, no seriously.
https://www.gamedeveloper.com/business/making-i-halo-anniversary-i-work
"And the reason to go with the Reach engine was -- I already explained that there's no real networking engine for the original CE. But I think, more importantly, if we came in with a new Halo game right in the middle of Halo Reach's lifespan and split the ecosystem like that, and split the player base, it would have made a lot more enemies than friends.
And this is supposed to be a celebration. We don't want to say, "Hey, stop playing this! Start playing this!" And we wanted to respect that."
Nevermind the fact that said excuse was 100% bullshit because Halo CEA was based on the Halo PC codebase, which had netcode.
So Halo MCC had all 4 games, on different revisions of the engine ported to one console, and done by different porting studios. This worked, except MP was a total clusterfuck because of this single design choice. That's not getting into the port bugs, including old port bugs from the PC ports of 1/2 (Halo PC was ported). In fact when Halo MCC launched, it still had the infamous netcode lead from the PC port. The current version has 6 games (now Reach and ODST are included) and get this; a UE4 powered menu.
There was also a rumor Microsoft was testing new matchmaking tech with the MCC as well at the time, and what Frank said later was some word salad about testing environments being set up improperly and then deciding "yep it works".
https://www.polygon.com/2017/10/21/16513450/halo-the-master-chief-collection-xbox-one-fixed-update-patched-343-industries
Pawlicker 🐾😹 /
npub1j4…6z0qp
2023-09-14 00:01:21
Author Public Key
npub1j4pgkf4mmw5uy7w57dvydrgkaarpdwt0e5w95vjgkshn2av4hs8qz6z0qpSeen on
wss://relay.noswhere.comPublished at
2023-09-14 00:01:21Event JSON
{
"id": "925812afc77c1ef5ace552c48c864621e8c05bd0eb796476d783ba4fc2e16bff",
"pubkey": "95428b26bbdba9c279d4f358468d16ef4616b96fcd1c5a3248b42f357595bc0e",
"created_at": 1694649681,
"kind": 1,
"tags": [
[
"p",
"dbaa6f910b00ccf3468e734b267a8ccc4828c560eb7f0e8e4346b7e3f5c40c7d",
"wss://relay.mostr.pub"
],
[
"p",
"f2b8cb5529d3f623a3bd7a053b38453969dcc24f107e06866c984d750b73491b",
"wss://relay.mostr.pub"
],
[
"p",
"f48cd0bd56a9ac499b792b31842b0a4d8e5146731090241f23efb1bc50042125",
"wss://relay.mostr.pub"
],
[
"p",
"8f1c6bd7d1c90aa59e8b31353d244c72a5827bd9b1bf89bdb7857b81916c14fa",
"wss://relay.mostr.pub"
],
[
"proxy",
"https://clubcyberia.co/objects/d4c21882-a309-487d-bfb5-30dc09d04cf2",
"activitypub"
]
],
"content": "nostr:npub1mw4xlygtqrx0x35wwd9jv75ve3yz33tqadlsarjrg6m78awyp37swdp6t6 nostr:npub172uvk4ff60mz8gaa0gznkwz9895aesj0zplqdpnvnpxh2zmnfydshx2cl7 nostr:npub17jxdp02k4xkynxme9vccg2c2fk89z3nnzzgzg8era7cmc5qyyyjsgzw2x2 nostr:npub13uwxh473ey92t85txy6n6fzvw2jcy77ekxlcn0dhs4acrytvznaqpfshsz \u003eI am a dumbass regular business apps developer, and I've managed to fix compile issues between Linux and Windows on a C++ project. I would imagine a professional games programmer could do this with ease.\n\nHere's where they fucked up. What happened was 343 wanted to keep all 4 games on the same UI with one main launcher for all 4, as opposed to having a single launcher load each game up and then handle MP/SP.\n\nI am not sure what the reasoning for this, but I suspect it was due to population count worries. This is why Halo CEA did not have MP, no seriously.\nhttps://www.gamedeveloper.com/business/making-i-halo-anniversary-i-work\n\"And the reason to go with the Reach engine was -- I already explained that there's no real networking engine for the original CE. But I think, more importantly, if we came in with a new Halo game right in the middle of Halo Reach's lifespan and split the ecosystem like that, and split the player base, it would have made a lot more enemies than friends.\n\nAnd this is supposed to be a celebration. We don't want to say, \"Hey, stop playing this! Start playing this!\" And we wanted to respect that.\"\n\nNevermind the fact that said excuse was 100% bullshit because Halo CEA was based on the Halo PC codebase, which had netcode. \n\nSo Halo MCC had all 4 games, on different revisions of the engine ported to one console, and done by different porting studios. This worked, except MP was a total clusterfuck because of this single design choice. That's not getting into the port bugs, including old port bugs from the PC ports of 1/2 (Halo PC was ported). In fact when Halo MCC launched, it still had the infamous netcode lead from the PC port. The current version has 6 games (now Reach and ODST are included) and get this; a UE4 powered menu. \n\nThere was also a rumor Microsoft was testing new matchmaking tech with the MCC as well at the time, and what Frank said later was some word salad about testing environments being set up improperly and then deciding \"yep it works\".\n\nhttps://www.polygon.com/2017/10/21/16513450/halo-the-master-chief-collection-xbox-one-fixed-update-patched-343-industries",
"sig": "75fa29d6fd4b71a7677480bb5b42b8ff36984636c91ea565dfcf65e3c56fb715f6535ceaeadb608d2a1b062463fdb2e0f052864a7894d33f961997e00c35eee7"
}