Akarias

If you are on a console you'll need to poke a shader refresh in order for the changes to take effect after you have poked your changes. eg: 0x828E676E for Halo 3. I made those in a few mins specifically for this thread. Those values also control other aspects of the shader(s) so be careful with what you change. Some control the UV unwrap of the bitmap etc. <--- Here you can see part of a map that I moved. <--- Finished product

Weapon numbers are a sprite sheet and they react well to tint changes iirc, so yeah. I remember something along the lines of changing the "display" shader will add a tint to the entire ammo counter on weapons like the AR. Or you can just go overboard like this. Its HO but same idea.

Just change the shader tint values. Go to the render model and check the shaders, one of them will be the numbers. Goto it and adjust the values there.

ya just asking for it mate

Run assembly as an administrator, right click "Run as administrator". Make sure to close any other programs that may have the file open.

Dimund got me interested in editing animations, so with a bit of help from dany I got the following last night. This is Halo Online but its the same idea for any engine on xbox. Its not much but the forum is a bit dead so.

Yes, this will work for campaign maps too. But something to note is that Halo 3 does not use the upgraded squads system that you see in ODST/Reach, to make these changes for Halo 3 you can either edit the [char] tags or swap the tagrefs in the [scnr] scenario character palette. To change what unit you play as do the following: Open assembly. Open desired map. Find the globals [matg] tag class. Goto the Third Person Representation block, edit to your liking. Note this block has a few different indexes: chief, arbiter, elite1, elite2 etc... Save and play.

Open assembly. Open desired firefight map. Find the squad_templates tag class. Edit the tags to your liking Save and play.

Thats not how it works, there is far more to it than just copy and pasting data between engine versions. Its a child object, added in the object properties tag HLMT.

There are no custom animations, everything that you see for HO is weighed onto existing rigs. Pretty much all console mods are made with render models that already exist in game but have been scaled and had new shaders added to them, those models are then attached as child objects to the original model. Say I have a warthog and want my wheels to actually be traffic cones, I would take the traffic cone and scale it to my liking and then attach it as a child object to the warthog model at the wheel nodes, then I would turn the wheels invisible by replacing or editing shaders. AI Playground is a BSP ported from campaign, the big empty cube gets used across a few maps. If you port it you will need custom lightmap bitmaps and some changes to the terrain shaders so you can actually see the BSP. The tools for creating custom models for the xbox 360 version of the engine do not publicly exist, if you are C# savvy you could take a look at TagTool's source code and get the render model replacement working for the xbox 360 version of the engines.

Assembly does not have a script compiler. There is more to editing scripts than just hitting a compile button. It was placed there as a joke years ago. You can either learn to edit scripts manually or wait until I finish a more user friendly and feature complete compiler.

I couldve sword you were a mod of some kind back then.

Fun fact: Basically everyone from 2011-ish came from S7. Zedd was even a mod there. Echs dee.

Even just the text files would be greatly appreciated, if they are what I think they are.