Content: Slate Blackcurrant Watermelon Strawberry Orange Banana Apple Emerald Chocolate Marble
Background: Slate Blackcurrant Watermelon Strawberry Orange Banana Apple Emerald Chocolate Marble
Pattern: Blank Waves Notes Sharp Wood Rockface Leather Honey Vertical Triangles
Welcome to Xbox Chaos: Modding Evolved

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

ShadeTH

Members
  • Content count

    64
  • Joined

  • Last visited

1 Follower

About ShadeTH

  • Birthday 04/27/1996

Profile Information

  • Gender
    Female
  1. Yo come backkkk

  2. PS3

    The bulk of the data in packages is definitely encrypted/compressed, but it's not zlib or gzip, I already checked.
  3. PS3

    PS3 ver consists of, for all intents and purposes, a single executable and a folder called 'packages' containing the following: I can't imagine the 360 version would be much different. Looking at these packages right now (they're not PS3 system packages, obviously). I'll post whatever I can figure out. They don't look like Reach or H4 cache files. EDIT: Headers vary in the same places, but it's hard to determine what they really mean. There's nothing denoting the EOF, surprisingly. at 0x800 there's always a 2048-bit long block of seemingly random data (easily a signature for the file). File positions might be relative. Halo cache files liked to do that. There's some sorta file descriptor, maybe a filetable at 0x1000. On ui_login.pkg it's "ui_login". On bootstrap.pkg it's got a few entries, including ones like: "map:bootstrap:root". Pretty neat. Also 100% useless but every package has "live tool_lib test pc_x64 41345.14.06.30.2046.live 14.06.30 2046" in the header. Probably like blam versions in the header.
  4. PS3

    http://pastebin.com/6hzdbLxL From the PS3 beta, so ignore cell stuff. I cleaned up most of the garbage and a fair amount of SCE junk too. So it looks like Bungie's new engine is internally referred to as Tiger (i.e. Project Tiger)? Also, only platforms in development seem to be PS3, 360, PS4, and Xbone. No PC builds, at least not in their main builds. Lots of internal stuff reminds me of blam engine cache files. That being said, I'll probably take a look at data files next. (Also apologies if the string dump isn't 100% allowed! I just wanted something good to kick this thread off with. Admins can edit that out if they wanna.) Anybody else been looking at this game?
  5. GTA V is, overall, really simple to make your own mods with. Think of a thing to change, search for it in the contents of common.rpf, and it's probably there. weapons are in ai/weapons.meta, loadouts are in ai/loadouts.meta, vehicle settings are in /handling.dat... it's all quite straightforward. Most of the files even have their own documentation clearly explaining what each field does. Plus the load order file tells you how to add mods after packing them. It's like they want us modding it.
  6. Also it's hard to do more than just speculate on how GTA Online will handle these things. We don't have the XEX for it or any of its files yet. GTA V had (almost) no protection, and I imagine it's similar. Rockstar knows what they're doing though.
  7. I think you severely underestimate golf cops.
  8. u ok pistol (figured out weapons mods in gta v i guess)
  9. Ascension and Alteration on 360 had the option to sync users' pokes so everyone would have a consistent modded experience - is there anything like this for Halo 2 Vista?
  10. I always imagined spartans didn't need to ADS since the reticle for their weapon would move around on their HUD as they moved it physically - thus the sights would be completely digital and no one would really look back. ...the only problem with that is hip-firing every single weapon all the time is kind of dumb. Who knows, maybe they're designed to be fired from the hip.
  11. I've heard that 180 joke nine times today. I am so done with xbox one.
  12. Ended up being a problem with my 5v line. Mystery solved.
  13. I recently built a SATA to 360 HDD connector to get 3.5" drives working on my box. I then ran a SATA power cable out from the PSU connectors on the motherboard. I'm using a Xenon PSU to make sure I'm not overloading it. Anyways, when I go to test this, the box hangs at boot and throws E68 (1010). With it still on the box's power, I can see it (and even format and access it) just fine with a transfer cable and the same SATA adaptor. (It also works fine over straight SATA, obviously. If I connect it over a transfer cable to the 360, it hangs on the devices screen before showing nothing. I'm convinced this is an issue with what's actually on the drive. I've tried completely wiping the disk (DBAN), but my 360 still won't see it. Any idea what this could be?
  14. Can't it be done with XBDM and the newest builds of Entity?
  15. Hard copies of games nowadays (with steam at least) consist of a digital key and installation media you don't even have to use because of the key. A Steam release would be awesome. It's probably not gonna happen though, as MS won't just let GFWL die a quiet death.