PESSOAS, NÃO POSSO JOGAR NO SISTEMA O SITE XBOXUNITY E PROENIX NÃO CARREGA ( COMO SE FOI DESABELADO - EU NÃO PODE ENTRAR EM 25 DE NOVEMBRO, 2022 Às 18:46 ATÉ AGORA )

ENTRAR DO TENTE:http://xboxunity.net/ 

Tente entrar:http://xboxunity.net/

  !!ALWAYS save a backup(s) of the original untouched/unmodded map(s) as the Very Final Step is to just put em right back on the ol Xbax/PC or the players will get booted/maps crash when going back online to systemlink (only mod/edit/assembilize the duplicate extra version of the .maps) - once you've done each .map and saved them you're set up to just transfer them to the ol Xbax/PC and Forge away any ol time!! 

The main goal in this Tutorial is to Finally get "100% Truly PHASED Forge Objects/Items/Weapons (maybe vehicles one day) along with an "Increased amount/Nearly Unlimited "kinda" Forge Budget" in ALL of the other maps BESIDES FORGE WORLD!

The "Unlimited Forge Budget" for Forge Worlds been around for ages (and also the steps for ALL the other maps though really), but I personally had the hardest time finding all the info, mainly in pieces, and most of it came out of trial and error as the info was pretty sparse. This pushed me to hopefully make this tutorial easy enough to read and friendly enough anyone can use it

We'll use Assembly to get all the "Extra Extended Number of Forge Object" in maps like Sword Base, Boneyard, Boardwalk, Power House, Reflection, ect.. You could ever want and we'll be using the "Small Crate Closed" in most of the following examples (actually the bigger one of crates as it is best for walls/floor/new walkways/inclines) it has most surface area. 

[Increase amount of Objects/Scenery/Budget Editing]

(aka "Entry Count")

Per each .map in Assembly go to:

1.  sncr  >  Sandbox Palette    -(scroll way down to it or keyword search "sandbox" it is fastest)-

2.  Far right of  >"Sandbox Palette"<  scroll through the groups/numbers (can use up down arrows after a click too)   6-7 (8) out of the "(8)" groups is:     

"ff_scenery"     -(it has the Small Crate in the forge "Scenery" section for certain maps like Sword Base)-

3. >"Entries"<   section: scroll down through the groups/numbers again (can use up down arrows again)  3-6 (7) out of the "(7)"  group is:       

"ff_scn_crates"    -(to give us all the crates here in the 3rd final section)-

4. >"Entry Variants"<     section: already has the "Small Closed Crate" aka "ff_scn_crate_small_closed" 

"ff_scn_crate_small_closed"   -( at  0-7 (8) )-

5. Increase the allotted amount of like 10 Crates to 50 or 300 or whatevs in the "Entry Count"

6. Drop each items cost down to to like $10/$5/$0 a piece not impact the overall budget, so all/more can be placed without exceeding the budget ceiling while forging we use the: "Entry Price"

!!!There is always of course going to be a magical limit to the amount of total Objects/Scenery you can forge onto a map and especially for my intentions of  making them playable online systemlink style, with too many Objects/Scenery/Gadgets/!!LIGHTS ESPECIALLY!! placed either the maps going to:

1. Not play at all online

 2. Have too many visual, audible, or other artifacts

3. Be so sluggish it's virtually unplayable scum biscuits, so yeah, might want to attempt to not got too hard yo, but hard enough for some exciting variations!! (I've placed nearly 300 crates map seem fine idk each .map has its limits though) !!!

[Making Objects/Scenery Phased]

(aka "Non-Physical in Map Editor") or (aka "Rigid Bodies" "physics_model" change) 

For making the Forge Objects "Non-Physical in Map Editor", aka truly in the "PHASED" editing physics state, so in Forge Mode you can smash em into the Walls/Them Selves/Make Forging Faster/Easier in these built in/non forge world maps:

Per -  Each .map ...then...  Each forge Object/Item inside each .map... go to:

- ("Small Crate Closed" - object/item for example)- again here as is best/largest for new floors/inclines/walls:

1.    bloc  >  objects\props\human\unsc\container_unsc_small_closed\container_unsc_small_closed

                                                                      (^^^is the actual Small Close Crate^^^)

2.  (first >"Flags"< section scroll down)  Check aka [X] out the check box for: " Non-Physical in Map Editor" 

!!!3. Select the "Phased" Physics state while forging to experience FAST/Instant phased objects 

(BOUNS for faster Forging Per each Object/Forge Item - You can also check aka X out the check box "Phased Physics in Forge" in the   "Multiplayer Object Properties" > "Flags" section.  This simply just makes the item already in the "Phased" physics state when forging and the whole point of the guide here so yeah no need to scroll through "normal" > "fixed> then to phased in the Forge editor, might as well hit this check box while here for each item yo)!!!

(different tag now>>>)
4.     phmo    >     (Per Each object/item/weapon/health pack)  > "physics_model" tag in the " phmo " 
5.  >"Rigid Bodies"<    (section change)    >     "Motion Type"  to>  "FIXED"   

!--!!!MAJOR SIDE NOTE SCUM!!!--!

The  ["Larger">] "Jersey Barrier", "Dumpster", and "Land Mine"  ..These 3 Objects NEED EXTRA LOVE to actually become "PHASED" and even then also have some more caveats/oddities as well....so...yeah....took me a bit to get these right...couldn't find info anywhere....and they're just and only kinda right...

[Jersey_Barrier] -- ("Larger/Square Edged one" as the "Jersey_Barrier_Short" is easily phased steps above) --

1. bloc to > "Non-Physical in Map Editor"

(different tag >>>)

2. hlmt >"Damage Info"< (section near far bottom) -- "Inderect Damage Section Index" -- from -1 to> 0

(different tag >>>)

3. phmo > Motion Type to> "Fixed"

!!Note: Have to "tap", "hit", "bump" the Jersey Barrier with another Object/Barrier/Item !!Just until it chips a piece of the corner of the jersey barrier!! Then grab the "Chipped Barrier" (before it's 100% damaged/broken and cannot be grabbed anymore). It will remain "Phased" until it is released/placed!!
 

[Dumpster {has hinged lid}] -(not "Dumpster_Tall" as for "Dumpster_Tall" easily "Phased" steps above)-

1. bloc to > "Non-Physical in Map Editor"

(different tag >>>)

2. phmo > Motion Type to> "Fixed"

(different tag >>>)

3. >"Rigid Bodies<" (section go to block>) -NODE EDGES- > [click the italic [i] for info dropdown] - then set COUNT to> 0 (it will wipe out/erase itself when set to 0)

NODE to> 0 (additionally as well)

!!!Note: When forging with the Dumpster NOT in "Phased" physics state> ("Normal" or "Fixed" physics selected) the Dumpster will do multiple crazy things "jump around", "fall through ground and hinge on lid", "rotate/lose lid" ... just use "Phased" as needed. You can go back to non-modded map ...then place in "Normal"/Fixed" as needed there/later don't forget!!!

[Land Mine]

1. bloc to > "Non-Physical in Map Editor"

(different tag >>>)

2. phmo > Motion Type to> "Fixed"

>"Phantom Types"< (section block) > [click the italic [i] for info dropdown] - then set COUNT to> 0 (it will wipe out/erase itself when set to 0)

--(Don't think you can Poke these changes and have to save, then migrated .map over to the ol Xbax scum)--

[Removing All Barriers/Boundaries simply for placing the Initial Load Out Camera/Forge Anywhere] 

(aka "Soft Kill/Insta Kill/Invisible/Out of Bounds Barriers/Boundaries") 

!!!(Will also be able to !!!Forge ANYWHERE!!!...but.....alas cannot play any other custom games online with anyone as there "Barrier/Boundaries" will be ON on there console....they all use the UN-Modded original .maps just as you should/and only can to play multiplayer when online/systemlink.....sux biscuits though.....don't know if a work around will ever come...sad...infinite sad days...

First and Second even Third off... Lord Zedd is the main mf man yo, and this is just my noobish saibot shadow breakdown of these/his almighty steps, where as the man himself has it all and more in his tutorial post titled " .map Modding - Getting Started "  

-There's >3< sections >(5 total block items)(3 on one tag/page...2 on the utter tag/page)< you "most likely" will want to "Remove Barriers/Boundaries" for ALL (5)....it's just the same process of -'zeroing'- out the >"Counter"<  in the info [italic [i] ] info drop down dialogue for each section/block:

[TRIGGERS] (kills or safe barrier boundaries)

1.  scrn  >   "Scenario Kill Triggers" and "Scenario Safe Triggers"  (fastest way to find them is search the key words top of the -scrn- page "scenario" or "triggers" ect... as they're near the bottom section of the -scrn- page)  

2. To the far right of each section for "Scenario Kill Triggers" and "Scenario Safe Triggers" hit the italic "i"/[i]  (symbol/box) to get the information drop down (than can be opened and closed with this button as needed)

3.  Set the >"Count"< number to "0" here for both > "Scenario Kill Triggers" and "Scenario Safe Triggers" <

[MOPP Trigger] ("suspected to be softkills")

1.   scrn  >  "Scenario MOPP Triggers"  (can continue using the fast search at top "scenario" or "triggers" ect...)

2. hit the italic "i"/[i] (again)

3. Set the >"Count"< number to "0" (again here)

[Design] (physical invisible walls) 

(different tag >>>)

1.       sddt  >   "Design MOPP Codes" and "Design Shapes 2"  (same quick search "design" now)

2.  hit the italic "i "/[i] (each/both again)

3. Set the >"Count"< number to "0" (each/both again here)

!!!To even be able to place a forge item(s) such as the Initial Loadout Camera outside the maps "normal" forging area, the BSPs MULTIPLE Flags -Per .map- have to be disabled as well (or it'll keep yanking you back into the "normal" forging areas of the maps when an items selected outside the "normal" area) luckily this too is pretty easy:

[ BSPs Flags] (enables forging outside "normal" forging areas)(let's us place our initial/other loadout cameras)

(different tag >>>)

1.   scrn  >   "Structure BSPs"  (near top of scrn tag/page)  

2.  Far right across from "Structure BSPs" scroll down through the groups/numbers (can use up down arrows after a click too)   0-2 (3)  (3tabs) <<or how ever many or whatever may they be as it changes per map, But SCROLL through EACH one and ensure ALL have:   "Prevents Forging"  unchecked/cleared check box in the Flags section (some are unchecked already usually) 

[[[Camera/General Tips]]] 

1. In Forge select "delete all" for the other "Initial Load out Camera(s)" and or use the main one to start 

2. Go crazy outside the normal map boundaries/walls/glass/ceiling if and when possible like on Sword Base use a sender/receiver/two way teleporter to go WAY out into the map to place your loadout camera

3. lots of things you can do with loadout camera(s) for teams/color/spawning times ect.... search around online for more in depth info tutorials

( !! If cameras pushed TOO far out on the .map it can cause cause BLUE/BLACK  screens aka no eye candy for your map when loading unless you're looking for that, but some you can place it mega far out!!!  Also always remember how many cameras or if you need to again delete all because once placed outside "normal" forging areas the camera is sometimes either very very hard to find again and or its normally visible camera icon for forging is now invisible !!!   ...Additionally...Sadly...Again..... No real sense in forging "out of bounds" here for systemlink play unless someone else has your same map + boundaries removed EXACT same way, and or is impossible all together if the items placed out here disappear, yanked back into "normal boundaries" (can sometimes turn off/flash/glitch in and out of existence) , or another actual useable reason is found/needed ) 

[Make Forge Monitor - Clip/Phase Through EVERYTHING] 

!!! This is sometimes good for objects get pressed too far into walls/scenery and turn off/flash/glitch in and out of existence. Sometimes though they're in the "Goldie Locks Zone" and even though you can fly through Objects/Walls/Everything and view the placed Object/Item at nearly every angle...it still will NOT let you grab it to delete it....only option then is delete all or revert to older save of a FORGE save if one had been made!!!  

--Per Each .map--

1. "bipd" 
(select the forge monitor\object)>>  "...monitor\monitor_editor"  

2. (section/block)>  "Physics"  > "Mass" = [1E+20]

3. "hlmt" 
(select the forge monitor\object)>>  "...monitor\monitor_editor"

4. (section/block)>  "Damage Info"  >  check the box for >  ["Cannot die from damage [x]"]
 

-(Don't think you can Poke these and has to be saved then migrated over to the ol Xbax scum again (or with ALL the changes all together in one Ultra Omega Kill shot now)-

[[[!!!Finished???]]]

!!! Always save a "backup" of the original map when using Assembly!!! This is where we need it!!! A "good" original "clean" version, only make/save changes to the duplicated/modded one to save yo self !!!

So once you've forged a crazy assparagus map.... ( I always save 3 "final versions when Actual Forging is going on as they sometimes can "overwrite" themselves EVEN if they're from say Forge World to a new Sword Base creation or vise versa [I don't remember exactly why this happens, simple reason,  totally forgot whatevs] because of manipulating items sometimes the 1st and 3rd get jacked so 3 saves is good as the second may be clean and what ya need...ya... 

.....So....again.........once You've made a masterpiece (which mine are far from that generally) ......

1.     Save yo masterpiece....

2.      Put your original "backup" of the "good" "clean" "unedited" version of the map itself back onto your ol xbax scum so you can go murderlize me online!!! 

These are basically the only things I have been trying to accomplish with my RGH lately as I had seen it done a little in the past but currently, I personally prefer the ol RGH Scum Systemlink over the PC MCC actually and it's supper easy to get the "Unlimited Forge World" action going and have been doing so for years now, this, opens it ALL up in a way!   So these are some fairly basic things probably all over the site here for years ( now again explained probably poorly by me), and elsewhere that I for some reason had a very hard time finding/figuring out how to do as so many of us are still systemlinking. I did this to not only remind myself of the steps if I forget again, but hopefully help some other Systemlinkers make it slightly easier to make some crazier, different, and more compelling custom maps/games outside of the ol Forge World Scum...even if it is with a more limited but not nearly as so palette! Cheers to all hope to see you online sharing and creating scum, go hard!  

Anyway, I'll continue playing with settings and things and hope I just luck into it. If anyone wants to lend a hand or point me in a direction, I'd like the help.

Spirit dropships possibly triggered me since halo CE. 

mas você deve usar os links para baixar em dois:

MEDIAFIRE: https://www.mediafire.com/file/pbzw5bcog6l8hip/rodovia.rar/file

MEDIAFIRE ( MÁQUINA DE WAYBACK ): https://archive.org/download/rodovia1/rodovia[1].rar

https://gyazo.com/5bee10cbc433b1521b49cdec62645263

System.UnauthorizedAccessException: Access to the path 'C:\Users\Gaming\Documents\Snow Slayer Mod\Info\snowslayer_halo.map' is denied.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   at Assembly.Metro.Controls.PageTemplates.PatchControl.btnApplyPatch_Click(Object sender, RoutedEventArgs e)

I have only found older resources which give me the jist such as daeh, version num, file size but I am absolutely stumped on index header offset.

It's stated to be a 32 bit number on most available resources however it appears to be a 64 bit number when comparing raw hex values to Assembly output.

This has been absolutely infuriating for the last week.

I have a map file(modified beachhead map with AI enabled) I have managed to put together with a few older guides -- the `index header offset` I am seeing is 00000001`CA4A174C when properly interpreted.

This matches assembly's output; Problem is this address is out of range for the map file, using the process base address in debugger it points to junk or non accessible memory.

My understanding is I am supposed to use this offset to find a magic that would help me translate all further ptrs in the map.

I'm trying to write more complex scripts that could be quickly edited & also learn about lexing/parsing in the process.

Does anyone have some knowledge on the back end of modding GUIs?

Im attempting/wanting to modify the "edit coordinates" feature while forging more specifically the "Edit Coordinates > Nudge (X,Y,Z width, depth, height)"

As an example: Placing a Crate/Object at the very bottom of a map it's coordinates for "height" or "Z" might be 0.0 and increasing it by one increment would be 0.1........Wow...yup........

But point being, is that theres is a Lot of Range between 0.0 and 0.1 and in a multitude of cases when forging (even "perfectly" snapping the coordinates in to exact matching numbers) object still are slightly off/not aligned...causing peeps like me to manually slam the object around untill..it does eventually align perfectly hence "Theres a LOT of Range between 0.0 and 0.1" 

So now...finally the questions...

Anyone know:

1. - First if it's even possibly to use Assembly to "Increase/Extend" the Range when  "Nudge"ing  an object? (as possibly the structure of the whole game is completely "Locked" to its standard coordinates and can't be edited)-( or if it's locked how can the extra range be preset/possibly accessible through other methods?)  

2. - If it can be edited, would it be !1! single edit to the "editor_gizmo" or somthing forge related/style/similar/map ...or... an edit to each individual forge object themselves? (as I'm unsure what to edit/where to look due to the state the object/gizmo/map go into once:

(1. objects grabbed by the forge editor gizmo 2. Then you go into the "Edit Coordinates > Nudge" portion of the menu while forging??? (idk im dumb scum)

3. - If it can be edited ((the sequal)) I'm supposing the "Extra Range" as it appears to be "quartered aka 1/4-ed" so Id like to edit it accordingly:

In between 0.0 and 0.1 >>>> now would be edited to have: 

0.0      >>   0.25    0.50    0.75  <<      0.1

[Even if they can't be represented onscreen while forging or it just itself takes way too much time (has to be done to each object) to add the numerical display of whats goin on under the hood in real time doesnt really matter much but would be just a cool bonus]   

Anyways.....anyway for me to manually add in that extra tiny tiny bit of range for faster forging perfection and alleviate even just a few headaches around for some fellow Reach Architechs? Thanks for any info at all in advance even possibily of no possibillity....probably shoulda just started and finished with this one paragraph...

I am not far away from releasing the first version of one of my Firefight mods for Reach, but I am having a lot of trouble dissecting the chdt files.

I have generally been able to tweak and test other things until I get a grasp of how they are controlled, but I am having a lot of trouble trying to make a weapon like the Plasma Repeater keep its crosshair when zoomed.

I was able to figure out how to do this for Halo 2, but they have changed a lot of the block structure since then.

Any advice is welcome.

I wanted to try other vehicles, but I gave up because there was no explanation.

I downloaded a patch file uploaded by bfixer117 users on the Xbox Chaos site, but it was not applied to PC MCC Forge Mode.

In addition, I would like to apply this to the campaign. Can't you see the history of the modified code?

The rate of fire of the AI is limited by the difficulty of the game. And even if I try to increase the rate of fire of the phantom_chin_gun, this one always shoots at the same speed.
The increase in the rate of fire only applies when I am a gunner. But when I add an ia in the turret, these are clamped. Anyone have any ideas to remove this bridle?
I mod on Assembly.
Thank you for your collaboration

(Sorry for my language i'm too bad ^^)

I've had to guess and check for the ai_place opcode. I've basically just been guessing function names and see if anything changes in the script. sorry for the broad explanation as I don't have too much time to go more in-depth.

I'll elaborate later down the road and keep this updated...

Arguments box, how does that work exactly? What would it take to create solid black values?

Thank you!

So I've been trying to get some imported campaign vehicles to work correctly for multiplayer on the Xbox 360 and have found out that many of them are either indestructible or simply despawn you as soon as they reach 0 health. This is a problem for multiplayer matches since it doesn't count as a kill. So if anyone knows how to make vehicles such as the Pelican and the human anti-air turret destructible and kill the players inside could they post a tutorial or if it's simple could they reply with the instructions in this thread?

Thanks so much.

I was making a map in forge on my modded forgeworld .map file. After placing about 400 items, the game no longer let me place any items. When I go to the item menu and select an item, it doesn't spawn at all and nothing happens. I looked through the file to see if there was some limit for all possible items that could be spawned and I didn't find anything. Just wondering if anyone else has an idea of what's going on. I did put a huge budget that I haven't yet reached and I also put a higher maximum amount of items I could place on the things I've been using, which I also haven't reached.

Thanks for the help.

Here is a video of a WIP mod i am working on that makes spawned AI use the maps pathfinding automaticly.

Just wanted to know if anyone had managed to find a way to force the crosshair to be the point where a shot is initially facing.

My dilemma is that I am trying to implement a weapon balance system that is focussed around linear recoil with absolutely no error or bloom.

So far so good? Well, no.

When you start playing around with a weapons' csdt file, you might notice if you set the rotation high enough that the weapon always shoots to the default crosshair position, even if the camera rotation has moved the crosshair above the default crosshair position. From this experiment, it is clear that the recoil in Reach is purely cosmetic, which is rather annoying when you compare Reach to Halo 2, where recoil works as one would expect.

Has anyone found a solution for this (some sort of Boolean that changes the behaviour maybe), or was recoil in Reach never properly implemented?

I have imported the "bfg" (big AA guns on Tip of the Spear) weapon from campaign into forge and am able to successfully spawn it without the game crashing.

I was also successful at making it usable, complete with adequate wide camera. 

However, I cannot seem to get sound working, at all. The core alarm, weapon charge, destruction sounds, nothing works.

I of course have the correct sound in the weap entry for the bfg weapon, and it is set to play on charge. I thought for a while that I had messed something up but it will actually play sound...some sounds.

It will play most entries from the snd! tag, but will not play anything from lsnd, which is where most of what I need is. I've gone into the charging sound entry in lsnd and made it so the "loop" entry has that sound, but nothing happens.

I have since tried just about any combination of settings on that page you can think of to no avail. Any assistance or suggestions would be greatly appreciated.

I'm sure I'm missing something, but I've been playing around with AI behaviours (char) and I can't find a way to make certain enemies like Elites or Grunts keep their damn distance.

In one of my mods I have made the AI far more capable at ranged combat, but they keep walking into melee range, becoming easy kills.

What I want is to define a minimum range at which point they will back off and continue ranged combat.

I hope someone has figured this out, it's really bugging me because I feel like it should just be a single variable.