Lol, it may not be broken as a CFW, but it's unstable and unreliable in many waysBUT IF IT AINT BROKE YOU SHOULDN'T FIX IT!!!11!
crystal glaceon sure will soonpls reply to my bait I'm getting bored
I'm using Luma because it seems to get new features first, it's stable, and has many features (Notably custom version string. My version string is my name, so I can prove my system is mine ^^)I understand reviving rxtools for people who still using it,but for people who are using luma3ds,why you want to use it?
Sorry,i meant why you want to use rxtools?I'm using Luma because it seems to get new features first, it's stable, and has many features (Notably custom version string. My version string is my name, so I can prove my system is mine ^^)
Honestly, I feel lima3ds route of combining decrypt9 and Luma into a single file is a bit dumb, as you have to constantly update luma and decrypt9 manually to have it be up to date. A boot manager with decrypt9 built in and a nice GUI would be amazing though. So it's kinda like rxtools, but since the cfw and tools are seperate, the user can update the cfw without the dev having to maunlly updating everything. Not sure exactly how this would work, but I can ask my dev friend if it's feasible. Would be a fun little project when I finish learning c. Just a little idea
The thing about decrypt9 is that it really does major update either based on the Guide/community demands or every month or two. But for the most part, there are updates that can be skipped or waited upon if a CFW were made from it.Honestly, I feel lima3ds route of combining decrypt9 and Luma into a single file is a bit dumb, as you have to constantly update luma and decrypt9 manually to have it be up to date. A boot manager with decrypt9 built in and a nice GUI would be amazing though. So it's kinda like rxtools, but since the cfw and tools are seperate, the user can update the cfw without the dev having to maunlly updating everything. Not sure exactly how this would work, but I can ask my dev friend if it's feasible. Would be a fun little project when I finish learning c. Just a little idea
There's no reason to lock this thread, brainstorming is happening.OMG, can a mod lock this thread already?
The thing about decrypt9 is that it really does major update either based on the Guide/community demands or every month or two. But for the most part, there are updates that can be skipped or waited upon if a CFW were made from it.
There's no reason to lock this thread, brainstorming is happening.
You don't have to use Luma. If anything options like ReiNAND or Corbenik can be used as well.What he means is, that luma frequently updates. It gets annoying to keep up with updates when your basing on someone else's code. So modularity is a better option. This could also mean anyone can use any cfw with this as well. ^^ more options, more customization!
You don't have to use Luma. If anything options like ReiNAND or Corbenik can be used as well.
Wait, are you talking about running Decrypt9 with a CFW in it or a CFW with Decrypt9 in it? Either method is a good idea, but which one are we talking about here?Well yes. But this is a cleaner way to do it code wise. Technically you could do it based on d9 updates. This is just more flexible as a code base and would require less updates overall. Because you only need to satisfy updates from one project over 2.
Same result lol. But for the sake of argument d9 with cfw.Wait, are you talking about running Decrypt9 with a CFW in it or a CFW with Decrypt9 in it? Either method is a good idea, but which one are we talking about here?
In that case, cramming something like ReiNAND into it would make more sense. It already lacks a menu and other features that Luma3DS has, so there won't be a need to strip any features. So from there, you can use the method R3Tools used to accomplish thisSame result lol. But for the sake of argument d9 with cfw.
In that case, cramming something like ReiNAND into it would make more sense. It already lacks a menu and other features that Luma3DS has, so there won't be a need to strip any features. So from there, you can use the method R3Tools used to accomplish this
If one is looking to replace the menu with D9, then I really suggest Corbenik. Corbenik's patching system is independent from the launcher, which makes it less like to break any of the patches.True. But you dont need to strip features if its modular. If you have a bootloader menu you can have that create the luma config file instead of luma. It just makes updating the cfw itself easier and the dev can focus on d9 issues. But yea one could cram in RN as it sees less updates, (as of right now lol.) However if one needs to make changes it gets difficult. This means just updating the a9lh.bin and thats it. Again this makes the code base more flexible to updates as it takes them off of their back.
Still leaves the issue of having to deal with updating the base code. Thats what im arguing here. I am in no way saying one cant do this. Im just saying its more practical to have a bootloader with d9 in it. That loads another cfw. That cfw can be swapped out at anytime for an updated one. So the end user doesnt have to deal with a cfw bug to be addressed by the rxreplacementfw and can instead just update the cfw itself. Makes it easier for everyone.If one is looking to replace the menu with D9, then I really suggest Corbenik. Corbenik's patching system is independent from the launcher, which makes it less like to break any of the patches.
They still using it because of misunderstanding that they think in order to use Luma3DS they have to go a9lh and that's not true that's what's stopping them from getting off itYou didn't even bother to read why I closed it.
I realize that I wasn't helping the community by discouraging RXTools. I was hindering it by discouraging future development of RXTools. Destroying community interest in the project was the worst approach to fixing it.
Considering just how many projects were made to update/replace it, there's still an obvious interest. And considering there are still people using it, shows that people want to use RXTools. They don't want to replace it something else, they want RXTools.