Well, it looked for a second like this was over as quickly as it began. I think it still has a chance.
So, I'm disregarding whatever the anti-me people were saying (I again didn't bother to thoroughly read overly acrid posts, because having tolerated too much of that sort of thing from Rune, I've decided to pamper myself and avoid dealing with those types of posts).
I said that million dollars crap was just to prove a point. Seriously, if anyone of you are still freaking out over that, chill out.
Someone didn't like my ants thing. Under certain light, you are an ant, if something said doesn't apply to you, and you so vehemently combat it.
Some people seem to be confused about this code thing (a code isn't always just a string of memory addresses and values that go in them). My website is littered with codes that weren't programmed, and are perfect examples of codes someone else could have made just as easily. You can HAVE those codes. I didn't spend weeks writing assembly for them.
The ones I did deserve more respect, though.
As a rule of thumb (Edit: proof reading this post, I realize this is a particularly interesting pun. Thumb is one of the processor modes of the NDS and GBA processor core, and I'm very proficient in Thumb programming as well, if you wouldn't guess. Anyhow, I suppose I should have said "Rule of ARM" instead), if you see an AR code that looks like this:
EXXXXXXX XXXXXXXX
EXXXXXXX EXXXXXXX
etc., where the E's are occasionally something else, then it's about guaranteed to be an ASM code. ASM codes are written in ARM source code (source code being that stuff protected by intellectual property laws), and compile to have lots of "E"s at the beginning of each line. This is because the ARM processor is designed to use the first four bits of an instruction (in other words, the first digit of every 8 digits) as the conditional requirement for execution, and "E" means "always execute". Most lines of code are always executed, as opposed to conditionally executed, so ARM ASM codes will have lots of Es in them.
Few more things (by the way, you guys post a lot in between my posts, and the resulting text blocks that make up my responses are getting tiring. Not sure if anyone noticed me slowly slacking off):
I don't have any form of Phantom Hourglass, so I can't make codes for it at the moment. I'd love to, though. If I ever do get a hold of it, fun will ensue.
I like jelbo's proposition.
Let me comment on it, line for line...
"have Rayder and anyone using Zeld's cheats in a .dat or whatever ask his permission first"
Well, if you'll read a few posts back, I GAVE permission. I said that you could post it all you wanted as long as you kept the file password secured, so that its distribution would be contained within the forum (let me elaborate on that: "within trusted members of the forum". If someone has just joined the forum and looks like the sort of person who would likely compromise this suggestion, it's probably a better idea not to let them in on the file. Hell, I could just encrypt a file with the aim bot in it and throw it up here for you if all of you are done bickering back at me).
"have Rayder and anyone using Zeld's cheats in a .dat or whatever only use codes permission is granted for (so no old aimbots or maybe aimbots in general because they can be greatly misused on WiFi)"
The first two suck, get rid of them. Really, it's probably in your best interest more than it is in mine. If you like them so much I guess you can keep them, but that seems kind of silly.
The good one: if you don't mind knowing that a wifi sodomizing code is in your .dat, leave it in, and contain the dang file so people like Rune don't just come in here and take it. And of course, after that, they'd spread it, and continue ruining wifi (as well as my reputation; not sure if anyone has seen what the people who have stolen the aim bot in the past say about me in the process, but it's disgusting). I remember I was particularly PO'd when someone used my aim bot on me.
"give Zeld (and any other code coder) proper credit for their work (in comment section under the cheat or in the readme?)"
Now, I read the readme, and Rayder says that it would be, to paraphrase, ridiculous to try and name everyone. He linked to the websites instead.
The issue here is that the R4 format isn't like the ARDS format. With an AR XML, you can put credit into the comment section of each code. It doesn't seem like an R4 has that feature. If it does, you'll probably want to use it. If not, well, drop it for now. If you consider everything else I've said, then it won't be a big deal (to me, at least).
It'd be nice if BSFree were updated more, because that site does a great job of referencing the code sources. Far better than any AR sub I've seen. Ripping credentials from there would obviously be an easy way of not having to sort out which code came from where individually.
Also, if you're wondering about the level of contribution between Hiei and I, I myself would probably guess that Hiei is more likely the better hacker. He seems to have a longer history of it. I've helped him out with the syntax of his ASM codes once, but that was just him getting used to a new hacking environment. By then he had already done what I'd estimate to be extensive N64 hacking (and probably hacking on many other systems). I think he mentioned doing a particularly clever ASM hack for a GBA game, too.
Hiei and I are pretty outshined by people like chishm, though. I don't know if Hiei would disagree with that statement, but chishm has the understanding of the DS hardware that I currently only dream of. I've done my share of research, though. I'll shyly admit to reading
GBATEK religiously for a while. Note: that sort of nerdiness is not easy to force oneself to do, and yet it's the kind of pain one has to go through if they want to teach themselves to make aim bots.
