This is getting silly, but let's address this head on.
Yessir.
I have denied no one credit, and your analogy is incorrect. It would be more parallel to this.
We do it something like this: Balanced Brawl created by AA and Thinkaman
They do it this way: Balanced Brawl is a project that seeks to rebalance Brawl. [Insert paragraph discussing Balanced Brawl here] This project was made by AA and Thinkaman.
Not at all. Take a closer look at the post. It would go more like this:
You do it:
Balanced Brawl created by AA and Thinkaman
They do it:
Bbrawl. Due
specifically to a request by the creatores
only because they asked, here is an
alternate title you can use if you
really feel like it:
Balanced Brawl created by AA and Thinkaman
See, this isn't about credit because we gave credit. There's no ambiguity at all at this point over what people did what. There's no disrespect for the coders behind all of this; we know exactly what they did. This is about formatting and nothing else.
And formatting is exactly the issue here. The formatting is the name of the code. If PW makes a code and he calls it "File Replacement 2.1a", people usually don't run off and call it "Code for replacing files from the SD". They call it "File Replacement 2.1a" because that is the name of the code.
I actually wouldn't care about that with the names. In the end that's unrealistic since 1-2 most popular names will end up being used. We put almost no work into making the name for this project and are completely unattached to it. We actually used a sarcastic, derogatory name for it for nearly the entire development (no, I'm not telling you what that is). In the case of names for things, a process of "natural selection" by which the names people actually want to use end up being used in the long run is perfectly reasonable.
But see, there's a difference between a nickname given by the community and an official name used to refer to it. Plenty of codes are referred to in different ways, like PW's file replacement code will be referred to as "the texture code", or the general super code will be referred to as the "general code". This is perfectly acceptable, because they are nicknames used in the community as nicknames. Nobody minds if you refer to the "Death Boundary Mod V2[spunit262]" as "Death zone mod engine" in normal talk. However, because you've changed it in an official project build,
that's why everyone is so upset. People put their full names on their resumes, not their nicknames. Similarly, people expect you to use the official names for your official release, not nicknames.
Regardless, any confusion this creates is on my shoulders, is it not? If people don't understand what these codes are, they'll pester me about it since I'm the one who is deviating, right? I have patience for such inquiries so, if I choose to subject myself to them (though there have been none in 110 pages), I don't see the problem. Anyway, with the dual formatted versions posted, I see literally no possibility of confusion. If people find the version I had confusing, they can look to the other version. Could you explain how a reader might come to not understand things? Thinking those two version of codes are actually different is reasonable I suppose; I'll make it more clear that they are identical. I actually have included a further note that should relieve you of all burden of resolving confusion. I accept as my personal charge the task of clarifying all confusion. We were already committed to the interest of the community through a conscious decision to provide unlimited technical support up to the limits of SWF global rules (I have answered several PMs asking how to get this working with no limit to my patience for identical questions). This isn't a big deal.
Regardless of the confusion, one of the main issues people have is still the
principle of the matter. People don't like what you're doing. Considering the ruckus it's been causing, I'm pretty sure it
is a big deal.
To move to addressing Paprika here...
There is a real dispute here, but we've kinda been dancing around on it. The real question to this is whether the way I have posted the codes is in violation of either of the two standards posts on this forum are to be held to: SWF global rules and the standards of ethics. I am very sure it meets the first one (which is unintersting anyway) so we must approach the second one. I feel when you produce a work you have an ethical obligation to credit those who produced component works. I feel as though I have met this ethical obligation, and in general I hold myself to high ethical standards on not just this but principles such as openness (notice Thinkaman and I posted what resources we gathered during development, for the benefit of the community and no personal benefit to ourselves, and we have posted easily modified .txt files of all versions of our code). I feel as though an attack has been placed on my ethics, in public forum as opposed to private channels, which is seemingly not mitigated by me making gestures that accomplish the effective purpose of the complaints. I don't want to be floating conspiracy theories here, but it feels like the purpose is to make me appear unethical, and that leaves me feeling offended. Some other gestures are confusing to me, but in the interest of civil discourse I'm not going to get into that.
Honestly, let's get down to raw principles. What ethical principles do you feel I'm violating by my method of doing things? I don't understand your position, and I legitimately don't understand the theoretical basis on which my most recent posting could be interpreted as inappropriate. The reason I'm going this far is really because I take great pride in my ethics, ethics of open development for the community with proper credit attributed on component works, and because of this I would refrain from making implied confessions of ethical impropriety without a clear ethical principle being laid against me.
I hope you understand. Over something like this, this has been bordering on the absurd for how drawn out the dispute has been, but it is only because of a desire to present a development platform of the highest ethical standards that things have proceeded as they have.
As for your entire "ethical" argument, the entire problem lies in the fact that
many people, especially those who are part of the Brawl+ project, believe that your "method" of doing things is blatantly stealing codes from other people and shamelessly using them in your set without giving due credit. In fact, one of the main reasons why the text for the newest Nightly Builds was withheld is solely because they do not want
certain projects from stealing codes that they have worked for.
As Paprika_Killer has said, if you simply used the standard naming for codes, there would be no reason for Brawl+ to withhold codes. Despite what you may think of your "ethics", the fact remains that several members of the hacking community and a massive number of people who play Brawl+ believe that you are not only refusing to acknowledge the coders for their hard work, but in fact
stealing their codes. Honestly, I'm not sure exactly what your problem is, since changing the names would take a few minutes and pacify a huge number of people. You seem to be rigidly holding on to the idea that you are absolutely right, despite the bad image that Bbrawl has, merely for failing to acknowledge the coders.
Also, providing an "alternate version" grudgingly "specifically" because of the "request" of "paprika killer" isn't doing much for your reputation. Rather than having the version which properly gives credit and acknowledgement as the
main version, you are attempting to put it off as the
alternate version. Truthfully, your version should be the alternate with the description of "titles rewritten to be easily understood and credits removed to save space".
The very fact that you have bothered to write a massive wall of text explaining why you are justified in not properly crediting the coders, rather than taking a few minutes of your time to properly credit the coders, is just one illustration of exactly
why many people think so little of you.