[mod]Shared and Mainmenu
[mod]Shared and Mainmenu
Apply these to the mainmenu and the shared.map. I made a post about this in the normal forums.
- Attachments
-
- mm&s.rar
- Here it is
- (2.68 KiB) Downloaded 259 times
Last edited by zwull on Wed Dec 28, 2005 9:47 pm, edited 1 time in total.
-
- Posts: 7
- Joined: Tue Nov 22, 2005 5:43 am
I said that I made a post about this mod in the normal forums, but. . . If these are applied, the mainmenu will have single_player_shared.map and shared.map added to it, it will also not have a blue filter. When the patch is applied to the shared.map, it makes it playable by anyone. You must have your new XBL updates off when doing this, they prevent you from playing these maps. I applied almost identical mods, if not copletley identical, a few months ago, but I didn't have time to test these, although I am almost sure they will work. Tell me if they do.
-
- Posts: 49
- Joined: Tue Apr 12, 2005 5:18 pm
- Location: MI, duh
-
- Posts: 49
- Joined: Tue Apr 12, 2005 5:18 pm
- Location: MI, duh
-
- Posts: 339
- Joined: Sat Apr 30, 2005 6:24 am
- Location: United States Posts: 9,999,999,999 1337: Yes, Very Much Team: T3am Guard14ns Gamertag: PigFarker
Maybe thats whats the PPF forPistonsMVP18 wrote:When i try to play shared.map i never am able to spawn
PigFarker - T3am Guard14ns Creator/Founder
WIP: | Cel Shaded Coagulation - 68% | Cel Shaded Headlong - 15% | Perfect Halo 2 Mongoose - 80% |
THE SPPF AND SERENITY WAR ENDS NOW WITH THIS!: | Serenity + SPPF <<<< PigFarker | Now, ENOUGH FIGHTING!
-
- Posts: 11
- Joined: Sun Nov 06, 2005 3:39 pm
ummm.
WoW this sounds a weee bit BS ish but i'll waste my time and check it out anywayz if by some rarity it does work gj!
Signature exceeded 34x14 pixels.
-
- Posts: 60
- Joined: Sat Nov 19, 2005 12:48 pm
wow i played single player shared but not shared, is there a diffrence?xenowisp wrote:you can play it but its dumb. it was origionally a test thing for bungie. its a bunch of characters, ships, weapons and stuff just standing around. and the map freezes often
you shouldnt need to patch your shared.map to play it though only the main menu
Um. . . first of al, no you can't play shared.map without the patch. Second of all, single_player_shared.map doesn't freeze at all, unless you kill the flood. And third of all, neither single_player_shared.map or shared.map are test maps, they were made so that they didn't need to have as big of map files, for example, they wanted to have all maps load the elite and masterchief characters from one map file. Why would they put a test map on the disc anyways. . . to waste space?
well the BSP was designed to test the charachters and stuffzwull wrote:Um. . . first of al, no you can't play shared.map without the patch. Second of all, single_player_shared.map doesn't freeze at all, unless you kill the flood. And third of all, neither single_player_shared.map or shared.map are test maps, they were made so that they didn't need to have as big of map files, for example, they wanted to have all maps load the elite and masterchief characters from one map file. Why would they put a test map on the disc anyways. . . to waste space?
-
- Posts: 410
- Joined: Tue Feb 24, 2004 11:22 am
- Location: Cantaloupe!
Time to clear some things up before a conflict brews...
shared.map is not a test map, but rather, a map designed to decrease map size, and along with it, loading time. single_player_shared.map is designed to contain any information shared across all maps, including campaign. The reason they didn't just use one shared map is that loading multiplayer maps without the shared cache ready to go would take 3 or 4 times as long as it currently does (which in my opinion is plenty long enough).
The stuff placed around shared.map would be weapons, powerups, MC, the arbiter, and elites. There would be no flood, no other covenant, being that none of those are used in multiplayer. The reason that anything is placed like that at all is that Bungie needed a way to get all of those objects into the map's hierarchy, and rather than make a "special-case" instance with these maps, inserting them into the scenario worked quite nicely.
Now, I can understand that single_player_shared may very well have been used to 'test' the game and/or the objects in it, being in that there is a player spawn there. However, I strongly believe that the map's main purpose is nothing more than to save time building, caching, and loading level-specific maps.
shared.map is not a test map, but rather, a map designed to decrease map size, and along with it, loading time. single_player_shared.map is designed to contain any information shared across all maps, including campaign. The reason they didn't just use one shared map is that loading multiplayer maps without the shared cache ready to go would take 3 or 4 times as long as it currently does (which in my opinion is plenty long enough).
The stuff placed around shared.map would be weapons, powerups, MC, the arbiter, and elites. There would be no flood, no other covenant, being that none of those are used in multiplayer. The reason that anything is placed like that at all is that Bungie needed a way to get all of those objects into the map's hierarchy, and rather than make a "special-case" instance with these maps, inserting them into the scenario worked quite nicely.
Now, I can understand that single_player_shared may very well have been used to 'test' the game and/or the objects in it, being in that there is a player spawn there. However, I strongly believe that the map's main purpose is nothing more than to save time building, caching, and loading level-specific maps.
Everything in this signature is false.
-
- Posts: 132
- Joined: Fri May 07, 2004 3:26 pm
- Location: california