There’s been some questions about this project, I’m taking a break from coding it to answer them.
s3 = abbreviation for Sys360
Q: What’s the difference between Sys360 and X360?
A: A paw-full of things, first off, it’s in a different language which expands my horizon on it. I am basically creating my own environment. To be honest, X360 is coded sloppy-like and it’s not fool proof. In s3, I am taking time to make sure my code is fast, efficient, and more reliable to not fail. Besides that, I am including classes and sources that are extra, besides the ones in X360. Also, it is to contain a full (CUSTOM built) Security library, big integer class, etc etc, which is cool for others, but mainly essential to the library.
In short: More, Better, and Faster.
Q: This is in native C++, will there be wrappers for it?
A: Of course there will be, I mainly did C++ for portability between OS, speed, and interface, but I know .NET whores would love it. Due note, I won’t make the wrappers until after the library is complete.
Q: Is it going to be open source?
A: I am not sure at the moment, not due to the usual kiddie “he’s done gon’ steal mah source which makes mah manhood feel small!” No, it is not that, in fact, it is because of kiddies like that that I MIGHT be changing things up here. And when I say that, I mean… Sys360 will have a spot on my site for documentation, everything detailed out on how to use, examples, and even fractions of source code. But, kids for some reason think “stream.Write(a few values here and there)” makes there program all god like and they don’t realize that anyone can know how the program mods the save by comparing a non modified file to one that was put through the program. So, they decide to not abide by the rules. Well, Sys360 will be… closed source, open documentation and fractions of source code. License will still apply, users will have to release open source. BUT, I am also thinking about paid user licenses, anywhere from 60 – 100 bucks PER APPLICATION for me to waive the open source policy on that program. Free user = open source, customer = not.
Again, this is all in decision mode right now.
Oh and, all closed source stuff would just be Xbox specific, anything else such as, Crypto API, biginteger class, IO class, etc etc is all going to be open sourced
Q: What does this mean for Le Fluffie and X360?
A: X360 I’m abandoning that trash :p Le Fluffie will be updated to work with s3, mainly for easy plug-in capabilities and… Windows GUI API is annoying as fuck…
Q: Can you teach me how to <do an xbox related topic>?
A: Sorry, no, I am not a teacher, I am not your slave, I juggle friends, raves, DJing, programming, school, and trying to find internships. No time for your stupidity.
Any other questions? Feel free to ask 
I cannot wait. I am fine with it being closed source with xbox stuff because I don’t really plan to look at your code for xbox stuff. I really wanna learn about IO in C++. Any ETA?
Meh, just someone else who wants to make some money …
People should be able to learn from what you did, since there is no Whitepaper or anything outside how the STFS Container works.
Good Luck with that
As I do agree with you that people should be able to learn, that’s not the case. From the past 1-2 years X360 has been out, 1-2 people maybe wanted to see how it worked, majority took it and wanted to use it for their own selfish reasons. I am including documentation (ex. whitepapers) on my site, which explains STFS. But, I’m just not releasing my code interpretation of it. Now, as with money, psh, I could care less, if I was in the market, I would put it at a better sell point, whose going to buy a $100 license per program? Barely anyone except some scrub.