Welcome to Brawl Code Sets! Basically, this forum is home for all of the code sets (also referred to projects) like Brawl+, Balanced Brawl, and more. Not only do the developers post downloads and get feedback for their releases, but this forum is also used to discuss projects and different topics outside of the norm.
You might be thinking, "Well, I have a good idea for a fun project!" Nice! I look forward to what you may put out. However, keep in mind these things:
* Have Leadership Skills -- Leaders of a project must be wise and outspoken. Usually, they also bring good ideas to the table, plus handle organization and make sure the coders know what they're doing. Most importantly, be a role model for future project leaders, don't reject every single little feedback you get. Which leads me to my next point...
* Be Professional and Nice -- Professionalism goes a long way. Be kind and curteous to people who show a lot of interest in your project, and able to give feedback. Don't discourage them by getting angry, flaming, trolling, otherwise people will view your project negatively.
* Have Knowledge of PSA/codes -- When you start a project, don't go into it without at least some knowledge of PSA and/or coding. Making a project and requesting codes that are impossible to do in Brawl isn't the way to go, unless you want the project to fail. We're only limited in what we can do still. Also, read up on terminology and learn! Obviously you don't have to know everything about PSA/coding, but it helps.
* Niche (Who Are You Appealing To?) -- What is your project appealing to? What aren't other projects doing that you could be doing differently? Brawl+ is catering to both the Melee and Brawl communities to add combos to Brawl while achieving balance and diversity. Balanced Brawl targets the Brawl community solely on bringing balance, like the name intends. Find who you're appealing to that another project hasn't.
* Don't Steal from Others -- When you make your project, it's okay to use codes already in place in other projects, but don't take PAC's or individual files from other projects and rebrand it as your own. It sets a bad precedent, and you are essentially taking other people's work. Also, don't associate yourself with other projects if they have nothing to do with yours.
Thanks! And hopefully, your project becomes the next big thing to hit the Workshop.
You might be thinking, "Well, I have a good idea for a fun project!" Nice! I look forward to what you may put out. However, keep in mind these things:
* Have Leadership Skills -- Leaders of a project must be wise and outspoken. Usually, they also bring good ideas to the table, plus handle organization and make sure the coders know what they're doing. Most importantly, be a role model for future project leaders, don't reject every single little feedback you get. Which leads me to my next point...
* Be Professional and Nice -- Professionalism goes a long way. Be kind and curteous to people who show a lot of interest in your project, and able to give feedback. Don't discourage them by getting angry, flaming, trolling, otherwise people will view your project negatively.
* Have Knowledge of PSA/codes -- When you start a project, don't go into it without at least some knowledge of PSA and/or coding. Making a project and requesting codes that are impossible to do in Brawl isn't the way to go, unless you want the project to fail. We're only limited in what we can do still. Also, read up on terminology and learn! Obviously you don't have to know everything about PSA/coding, but it helps.
* Niche (Who Are You Appealing To?) -- What is your project appealing to? What aren't other projects doing that you could be doing differently? Brawl+ is catering to both the Melee and Brawl communities to add combos to Brawl while achieving balance and diversity. Balanced Brawl targets the Brawl community solely on bringing balance, like the name intends. Find who you're appealing to that another project hasn't.
* Don't Steal from Others -- When you make your project, it's okay to use codes already in place in other projects, but don't take PAC's or individual files from other projects and rebrand it as your own. It sets a bad precedent, and you are essentially taking other people's work. Also, don't associate yourself with other projects if they have nothing to do with yours.
Thanks! And hopefully, your project becomes the next big thing to hit the Workshop.