Taking advantage of the added attention from people complaining about the Maps page!
Nothing has changed, except for the plumbing - bit thank you to @ExTerrestr1al for his piping skills, and big thanks to 343i for taking up the Mantle of Responsibility of General Motors' long-defunct Saturn division - nothing says quality, affordable luxury like biodegradeable plastic bodypanels!
Anyway, we've got some video for you this time around, courtesy of @brusky0086 - big thanks for the gameplay, can't wait to see how you treat it for the feature!
Built for the 1v1 contest from October, this map is.. fun! It may not have the most depth or complexity gameplay-wise, but it is still going to be a hoot taking it seriously, or casually!
I must end every paragraph with an exclamation mark!
Please have a go on it, it's a fun time for all and a tight little experience. Will be updating soon with minor fixes to a couple clambers and one light, but other than that, it's good to go - enjoy!
The past ------ for greater understanding and immersion in the experience, read the lore below!
-- -- -- --
So, looks like Halo 5 is a broken, steaming, pile of General Motors during the 80s and 90s-style ****, engineered by people who are far too expedient with their logic. Like me!
Basically - the downloadable version linked here is broken. Why? Because 343i seems to have designed the intro cams around a 'ROUND 0' kind of thing. This is only a hypothesis, but what's happening is that, because the Shuttle spawns as a physical object at the beginning of the match waaaaaaay out in the desert in a box made of scripted blockers, and we think there is a 'round 0' during the intro sequence, the time-remaining scripting begins exactly at the beginning of the camera sequence, because there is less time left in that 'round' than it is designed to wait for - as such, the shuttle sequence begins once the map loads, and the scripting continues on into 'round 1', landing the shuttle within 20 seconds of the match start, rather than waiting 5 minutes.
It also causes the Rockets to spawn at the very beginning of the match, when they are normally supposed to spawn when the shuttle arrives, 5 minutes in. This drastically changes the gameplay and severely limits both players' options at the beginning of the match.
On top of this, the regular scripting of the blockers takes place as scheduled during 'round 1' as well, but there is no second shuttle (it's a normal physics welded object, and is not set to respawn, as it is supposed to stay in that corner of the map) - what happens is that the blockers arrive, along with the accompanying 'sweeper' piece. This sweeper piece ends up sweeping away the shuttle that already landed, and may result in death
Watch THIS for visualization of the intro sequence.
And see this photo for the effects of a sweeper block on a normal physics block - keep in mind I took this immediately after it (I) killed the player I was testing with.
It's an easy fix - just delete all cameras and save as a 'GIMP' version - but until we get confirmation from all judges, we cannot save a new copy or link it to this page.