Homebrew FatesHax, would it be possible?

[The Catboy]

Uhg. Why do you all repeat the same crap over and over again? Spam is annoying, and I know how hacks work...

Sent from my LG-H811 using Tapatalk

Because people who know what they are doing are all going to universally agree. We get these kinds of threads at least 3 times a week, all the same thing, "OMG! Thie game crashed! Can we hax it?!" and the short answer is no.
It requires a lot more than just a simple crash to make a game exploitable, otherwise every single game could easily be used as an exploit, as every single game can crash.

 

[Docmudkipz]

 

[Bubsy Bobcat]

Uhhh, is this thread still a thing?

 

[Seriel]

Because people who know what they are doing are all going to universally agree. We get these kinds of threads at least 3 times a week, all the same thing, "OMG! Thie game crashed! Can we hax it?!" and the short answer is 98% of the time, just a no.
It requires a lot more than just a simple crash to make a game exploitable, otherwise every single game could easily be used as an exploit as every single game can crash.

But what if this game was an exploit, you would be stopping development before it even began.
This is pretty extreme but what if that guy (i forget his name but he made basehaxx) posted saying they thought they found an exploit, if you all hated we would have no basehaxx, and I wouldn't have been able to hack my n3ds!

 

[seijinshu]

This guy uses unmodded system and games. Read posts before spouting useless crap.

Sent from my LG-H811 using Tapatalk

 

[Docmudkipz]

This guy uses unmodded system and games. Read posts before spouting useless crap.

Sent from my LG-H811 using Tapatalk

Thats not the point I made. Im saying someone visited his castle and gave him an item not in the base game, not that he modded his. That post was probs more useful than anything else youve posted in this thread

 

[seijinshu]

Because people who know what they are doing are all going to universally agree. We get these kinds of threads at least 3 times a week, all the same thing, "OMG! Thie game crashed! Can we hax it?!" and the short answer is no.
It requires a lot more than just a simple crash to make a game exploitable, otherwise every single game could easily be used as an exploit, as every single game can crash.

This is what you all did to hykem. Let someone with knowledge take over. I don't tolerate useless spam.

Sent from my LG-H811 using Tapatalk

 

[The Catboy]

But what if this game was an exploit, you would be stopping development before it even began.
This is pretty extreme but what if that guy (i forget his name but he made basehaxx) posted saying they thought they found an exploit, if you all hated we would have no basehaxx, and I wouldn't have been able to hack my n3ds!

The issue with Basehax was lack of evidence and questionable video. Once a clearer video was presented with better evidence, things changed. You can't just accept everything without actual evidence.
A random crash is not an exploit. They also need to see it if can be replicated and not attributed to issues like hardware issues, save corruption (from say shutting your system down well saving,) ect. Then actually determining if you can run exploitable code through that crash. As I stated before, a crash does not an exploit make.

This is what you all did to hykem. Let someone with knowledge take over. I don't tolerate useless spam.

Sent from my LG-H811 using Tapatalk

I am not against any exploits, if anything I want more of them. But I am against randomly making a new thread with every single game crash without an attempt to actually test it's actually an exploitable crash. People who actually know what they are doing can be contacted before hand to see if they can replicate the same crash and make an exploit. Every single homebrew dev for the 3DS either has a Twitter or a GBATemp account that they can be contacted on. Which would honestly be a better idea instead of making yet another speculation thread because a game crashed.

 

[seijinshu]

The issue with Basehax was lack of evidence and questionable video. Once a clearer video was presented with better evidence, things changed. You can't just accept everything without actual evidence.
A random crash is not an exploit. They also need to see it if can be replicated and not attributed to issues like hardware issues, save corruption (from say shutting your system down well saving,) ect. Then actually determining if you can run exploitable code through that crash. As I stated before, a crash does not an exploit make.

I am not against any exploits, if anything I want more of them. But I am against randomly making a new thread with every single game crash without an attempt to actually test it's actually an exploitable crash. People who actually know what they are doing can be contacted before hand to see if they can replicate the same crash and make an exploit. Every single homebrew dev for the 3DS either has a Twitter or a GBATemp account that they can be contacted on. Which would honestly be a better idea instead of making yet another speculation thread because a game crashed.

But the problem is I don't need to flood Smea's seemingly unused gbatemp account, and I refuse to get a twitter account...
And I've said I can't test. I'll present a YouTube video once I'm testing things.

Sent from my LG-H811 using Tapatalk

 

[Olmectron]

Tomorrow I'm returning my new 3ds and once I transfer back to my o3ds, I will begin investigating.

Sent from my LG-H811 using Tapatalk

Didn't you know you CAN'T make a system transfer from a N3DS to an O3DS?

Close this thread, you won't be able to investigate.

 

[shipwreck5]

Woooow u guys are calling seijinshu dumb but u are complaining about wasting his time. he's made up him mind and probably won't change it. Doesn't that mean ur wasting YOUR OWN time? Its funny.

 

[seijinshu]

Didn't you know you CAN'T make a system transfer from a N3DS to an O3DS?

Close this thread, you won't be able to investigate.

Hmm. Then... Plan B, try restoring NAND backups. I ain't closing until I prove that I can't exploit this.

Sent from my LG-H811 using Tapatalk

 

[The Catboy]

But the problem is I don't need to flood Smea's seemingly unused gbatemp account, and I refuse to get a twitter account...

Sent from my LG-H811 using Tapatalk

Then your suggestion is going to fall on deaf ears. Most of the Temp just wants results without actually helping, that's a community problem.
I actually would be willing to look at this crash if you are able to send me a save file and see if I can replicate the crash. I would need the save file because I am no where near that chapter in the game. If we can get more people to actually replicate the same crash, maybe there's some legitimacy to a hack through this game. Or maybe it's just a crash, it's hard to tell if we don't have something to actually look at.
I am not trying to be mean and I am sorry if I came off as mean. Like I said, I see these threads at least 3 times a week. And no one is willing to actually go the extra effort in presenting a decent case. It's nothing personal towards you or your thread.

 

[seijinshu]

Then your suggestion is going to fall on deaf ears. Most of the Temp just wants results without actually helping, that's a community problem.
I actually would be willing to look at this crash if you are able to send me a save file and see if I can replicate the crash. I would need the save file because I am no where near that chapter in the game. If we can get more people to actually replicate the same crash, maybe there's some legitimacy to a hack through this game. Or maybe it's just a crash, it;'s hard to tell if we don't have something to actually look at.
I am not trying to be mean and I am sorry if I came off as mean. Like I said, I see these threads at least 3 times a week. And no one is willing to actually go the extra effort in presenting a decent case. It's nothing personal towards you or your thread.

I can't get one, but I WILL attempt to replicate the issue, and then go from there.

Sent from my LG-H811 using Tapatalk

 

[seijinshu]

Woooow u guys are calling seijinshu dumb but u are complaining about wasting his time. he's made up him mind and probably won't change it. Doesn't that mean ur wasting YOUR OWN time? Its funny.

Well said. I have all the time to waste. I have no job, nor will I have one until next summer. I am just doing the stuff I've enjoyed for all my life. No one will stop me.

Sent from my LG-H811 using Tapatalk

 

[Docmudkipz]

I can't get one, but I WILL attempt to replicate the issue, and then go from there.

Sent from my LG-H811 using Tapatalk

Again, unless you know exactly what was in his inventory when it crashed then you wont get anywhere.

 

[Olmectron]

I can't get one, but I WILL attempt to replicate the issue, and then go from there.

Sent from my LG-H811 using Tapatalk

How would you replicate the issue? Play the exact same way as your friend, recruit the same units, get the same inventory, level up the same way, have the same My Castle, and so on? That's insanely hard, if you think about it.

 

[GerbilSoft]

I haven't actually disassembled the code so I can't say whether or not this is correct, but it sounds like something like this is happening:

void load_item(int item_id)
{
    char item_filename[64];
    sprintf(item_filename, "/data/items/%d.bin", item_id);
    FILE *f = fopen(item_filename, "rb");
    assert(f != NULL);
    /* etc */
}

Since it's trying to load an item from a customized version that doesn't exist in the original, it's failing to open the file and hence crashing with an assertion. Assertions aren't exploitable.

 

[seijinshu]

How would you replicate the issue? Play the exact same way as your friend, recruit the same units, get the same inventory, level up the same way, have the same My Castle, and so on? That's insanely hard, if you think about it.

Save editing is a somewhat simple hex edit away, I hope. It has been long since I did some dirty modding work, but I can get a result, positive or negative.

Sent from my LG-H811 using Tapatalk

 

[seijinshu]

I haven't actually disassembled the code so I can't say whether or not this is correct, but it sounds like something like this is happening:

void load_item(int item_id)
{
    char item_filename[64];
    sprintf(item_filename, "/data/items/%d.bin", item_id);
    FILE *f = fopen(item_filename, "rb");
    assert(f != NULL);
    /* etc */
}

Since it's trying to load an item from a customized version that doesn't exist in the original, it's failing to open the file and hence crashing with an assertion. Assertions aren't exploitable.

Hmm. I will try my other ways. Not about corrupted items, but it is a start.

Sent from my LG-H811 using Tapatalk