External Memory
Neo Member
Then tweak it by gametype, like I said. Otherwise, you're testing on the assumption that 343 will either drop PO from the playlist or add map-specific tuning with a TU, which is a big if, ideal conditions or otherwise. PO is THE main condition of Infinity Slayer, and the entire new scoring system. For anything other than initial tests, again, I find not using tuned PO when you can set it up by gametype to be pointless. Approximate the tools the devs have by whatever means needed, the Forger or his pals are typically the ones running the playtest so it's not as though adding the variant to the specifications is that hard for playtests.
You either misunderstood my point about the map maker suggesting the tunings for personal ordnance, or you really think 343 won't take the community map and tweak according to the designer-suggested personal ordnance options, and will instead wait until we also have the tools to set map-specific PO for whatever reason. Either way, whether you're reccommending a map to be used without PO, or with PO that has been tuned, you're asking for players to use variant settings, so why not get the best approximation of how you would tune the PO if you had the map-specific tools? And what better way to recommend to cartographers and 343 sustained producers what the map PO should be, since they can tune it, than just putting it in a bloody gametype for your map? Throwing out the proverbial baby with the situational bathwater here just seems the sort of stubbornness and obsessiveness symptomatic of many Forgers. The workaround seems clear enough here.
Whatever the fix people decide to use to make their maps work, I do sincerely hope 343 plans to incorporate community maps before a title update; if not, I hope it's not far off. People won't want to play community maps with messed-up Fiesta ordnance, but they will want to play them with tuned PO just as they do judging by population in the default playlists.
No, they definitely do. At least vanilla Infinity Slayer does. There's no option in-gametype for Slayer to turn weapons on-map off, actually.
I just played an Infinity Slayer game (default on-disc gametype) with weapons on the map. I have the film in my share if you need proof.
What gametype were you using? Did you save the MM gametype from temp. history, for example, or use the one on disc? Or were you using Dominion off MM/on-disc for example? Were the weapons set to phased or fixed physics, or normal/drop placements? It's possible that some on-disc gametypes or MM gametypes are hard-coded not to spawn weapons on map, but definitely not on-disc Infinity Slayer.
There's a bit of misinformation and miscommunication (and resulting uninformed butt-frustration) happening because people are heading off to post at the drop of a hat, first problem, and then also not leaving repro info for their given problem. In the game I played, the weapons were set to fixed, so any normal-physics placements likely just de-spawn a few seconds after shifting in the start of the match. Check your temp history in films to confirm, and we can test whether the same fixed-physics weapon spawn issues in Reach are still in Halo 4.
EDIT: Actually, just tested this in on-disc Infinity Slayer, and all weapons, whether set to normal, fixed or phased, spawned just fine, and swapping one fixed or phased weapon for another didn't result in the dropped weapon floating mid-air like in Reach. Same goes for off-host, if that makes any difference. Some gametypes, like Flood, do override weapons on map and are hard-coded as such, unfortunately. Just another thing on the long list of missed custom game opportunities for 343.
