HaloMods "Classic" Read-only Archive

I'm just curiouse if this is an avenue the average modder can take to move closer to making ACTUAL mods. Usermap modding is fun, but very limited.

I know that it would be naive to believe that this has never been looked at, and i don't. I'm just curious as to what people have learned about it and why it can't be used as a method for us poor suckers without a dev box.

I'm pretty sure what's in the cache is pretty highly encrypted... I could be wrong though seeing that pretty much everything I know about hacking, modding ect. was learned on this site.... justt my 2 cents

From what I have heard, the cache is just as protected as the maps themselves.

Eaton wrote:Form what I have heard, the cache is just as protected as the maps themselves.

Uh...

When the game starts, the cached file is checked again by the same security method thats holding us back from nodding on a retail.

ah hah!... that sucks

Oh well at least now i know, and knowledge is power...

Also, unless I'm mistaken, there wasn't ever anything done with Halo 2 cached maps. I never recall seeing anything of that sort, unless it was a fairly recent development, so the subject description is misleading.

http://forums.halomods.com/viewtopic.php?t=79155

jumped the gun and mis-read that my bad... We probably could have though it just made more sense to mod the .map's... at least i would think

You first need to be able to access to the 360 HDD from a computer while its running with the 360 too.
I tried unpluging the 360 HDD while running on H3 it rebooted, i guess security system.

why would u need to do that? It doesn't delete the cache when u reboot...

neodos wrote:I tried unpluging the 360 HDD while running on H3 it rebooted, i guess security system.

It's like that even if you're on the Dashboard...
It's not so much a security system as it is you're physically removing shit that it needs to read from.

If it wasn't something like i said it would crash not reboot.

Because it checks the cached mapfile but what about modifying it right after it checks for signature?

You realize that Halo 3 can run without a harddrive, right?...
It reboots as a precautionary measure so end-users aren't met with crashes with such simply performed tasks.
Think about what some random father would think if his 360 crashed while he was playing Madden '09 because someone bumped the HDD out.
It's just a precautionary measure to prevent against a number of damaging prospects.

And unless you plan on running homebrew apps on your 360 natively, I don't see how you plan on modifying the cache in real time, or at least gaining access to your 360 via sockets like on a devkit.
Also, there are numerous security checks that occur in real time.
i.e. the seven checks to verify users legitimately have the Recon armor unlocked, several of which actually occur while you're playing a game.

You're wrong on so many aspects it's a bit breathtaking.

ouch... It was just speculation...

alas it seems that H3 modding for the average jerk is not gonna happen anytime soon

patience is a virtue, and i have plenty of it

if you were determined enough i believe it is possible to turn a retail 360 into a devkit, i believe i could be very wrong.

CompKronos wrote:if you were determined enough i believe it is possible to turn a retail 360 into a devkit, i believe i could be very wrong.

Suthfering suckatash...where did you hear that from!?

Veegie wrote:You realize that Halo 3 can run without a harddrive, right?...
It reboots as a precautionary measure so end-users aren't met with crashes with such simply performed tasks.
Think about what some random father would think if his 360 crashed while he was playing Madden '09 because someone bumped the HDD out.
It's just a precautionary measure to prevent against a number of damaging prospects.

And unless you plan on running homebrew apps on your 360 natively, I don't see how you plan on modifying the cache in real time, or at least gaining access to your 360 via sockets like on a devkit.
Also, there are numerous security checks that occur in real time.
i.e. the seven checks to verify users legitimately have the Recon armor unlocked, several of which actually occur while you're playing a game.

You're wrong on so many aspects it's a bit breathtaking.

So that's whaty i though at first it reboots as security then you did you fucking came bother...

H3 modding could be for anyone if there wasn't assholes like we just had an example.

Veegie wrote: Also, there are numerous security checks that occur in real time.
i.e. the seven checks to verify users legitimately have the Recon armor unlocked, several of which actually occur while you're playing a game.

You're wrong on so many aspects it's a bit breathtaking.

I didn't even know it was that serious.

neodos wrote:

Veegie wrote:You realize that Halo 3 can run without a harddrive, right?...
It reboots as a precautionary measure so end-users aren't met with crashes with such simply performed tasks.
Think about what some random father would think if his 360 crashed while he was playing Madden '09 because someone bumped the HDD out.
It's just a precautionary measure to prevent against a number of damaging prospects.

And unless you plan on running homebrew apps on your 360 natively, I don't see how you plan on modifying the cache in real time, or at least gaining access to your 360 via sockets like on a devkit.
Also, there are numerous security checks that occur in real time.
i.e. the seven checks to verify users legitimately have the Recon armor unlocked, several of which actually occur while you're playing a game.

You're wrong on so many aspects it's a bit breathtaking.

So that's whaty i though at first it reboots as security then you did you *** came bother...

H3 modding could be for anyone if there wasn't assholes like we just had an example.

While i may agree he was a little harsh i don't consider calling a staff member an a-hole to be wise.

Peace and love ya'll... peace and love

Bye.