Open Classic Theme

I really don't care what you and your arbitrary group of people think about me. I won't bother to answer to you with anything productive from now on, if you keep making it about this. You made your point, I disagreed with it. That's that. I'm not interested in this conversation.

Alright, thank you. And no, I don't hate you. I just want to conclude this discussion is all.

Release version 1.5:
* Separated all mods into scripts for each specific task, to make progress display more accurate, and to not have to implement all functionality.
* Added init task to applicable mods.
* Added StartOrderPre and StartOrderPost to config bat, which allows to set the order in which components start.

You have pretty much reached my limit now. Like seriously, make your own tool, do not reference Simple Classic Theme again, and shut the fuck up.

Disliking something is fine, but being a pretentious dick about it is absolutely not. Your tool sucks so much that you have to start fucking lying to people about its place compared to other software. Making the system shell Classic Themed, having a configurable installer, downloading components when needed, staying within a folder and expandability are ALL key-features of Simple Classic Theme. Even being open-source does not make your software 'better' than SCT in any way, shape or form. You seem to combat anything we say to you, yet you still implemented Classic Theme Tray after I suggested it, saying 'thank you' as if you do not absolutely despise me. Your indignant behavior is sickening everyone on this, and other communities.

Let me make it abundantly clear again: BSCT is not better than Simple Classic Theme. It is not a functionally equivalent replacement for it. It does not meet the quality standards that Simple Classic Theme passes through in its development. It is only an alternative if you do not like SCT somehow. Your tool is not even its own piece of software: because of the way it is built, it requires some other application to enable Classic Theme for it, making your method pretty much equivalent to anixx's method described on the ExplorerPatcher discussions page on GitHub. Do not pretend you reinvented the wheel.

The only reason you were able to make this software is because of the knowledge and resources available in this community. We are all very dedicated to getting Classic setups working on newer versions of Windows and we have done a lot of research into it. To come into the community that did all the research and abundantly ignore everything they say, makes you yourself ego-centric. Everything has to be about the fact that you dislike Simple Classic Theme's closed-source natures, while nobody else seems to give a shit. Yes there have been concerns, but I intentionally said I will not discuss the reasoning because the development cycle will only improve from it. The rest is not important

Your naming makes this whole situation even funnier. If you had just said that you do not agree with my decision to close-source SCT, and had uploaded your own thing with an original name, I would have totally praised you for making a lighter alternative. Yes, that is the only thing that makes this a feasible script for me: it is lighter than SCT in disk footprint. 

I do not need to be enlightened with your imaginative reasoning for why you are in the right here. You are not and I think everyone here agrees with that. Spare me the painfully stupid argument, and get your shit together. You are not better than anyone else here, so like everyone who made a contribution to the community, make up an original, non-derogatory name for fuck's sake.

This does not surprise me; bat scripts are quite powerful, but it's easy to make a coding mistake that damages the system. This is aggravated by the lack of a debugger (there is one I think, but it is not very powerful anyway).
I know what I'm talking about, I'm working on a series of scripts quite similar to those of Fierelier, I have to check everything in detail (it's also because I'm less experienced in this programming, but still). For your system, I think it's fixable though, you just have to figure out what went wrong, to do it the other way around.

Fierelier I think it would be good to test the scripts in a virtual machine before publishing, even if you seem more experienced than less in bat scripts.

And after all this mess I do not trust you to be able to fix my computer after what your program did to it. All of my colors are messed up all of my programs are messed up I cannot uninstall your program. You have permanently set my configuration to your windows color scheme and even after uninstalling it I cannot put it back to the way it was before.

herit://that1cutie I've had it with you. Since you're not willing to go into the issue in detail and given your obvious bias, I'll assume you're lying. If your issue IS real, you're a condescending piece of work for thinking I couldn't fix it. You're not here for any productive reason, so just stop bothering me. All you do is stir up drama with your constant, useless blabbering.

Also, the URL is based on the thread topic. Create a "Better Simple Classic Theme" thread and see the URL for yourself. And don't come up with some twisted explanation again to somehow implicate some bad intention. I'm tired of your baseless theory-crafting.

The Jackal Imagine having an opinion, I feel I have been liberal enough with it. People are horribly blowing it out of proportion.

This is just a constant barrage of hate, here. I feel people are being oblivious to the fact that SCT is not some complicated program. It isn't due as much credit as you all give it. The author said himself, it's simple, and the methods are publicly known.

Release version 1.7:
* Changed all remaining branding from BSCT to OCT.

Release version 1.8:
* Automatically revert color scheme on uninstallation.
* Add utility for enabling 3D borders in themes folder, since choosing a theme disables them (this is only visible after logging out and logging back in).