This is a very basic introduction to the IRC channel #wiidev on EFNet. We would like you to take a few minutes to make yourself familiar with its purpose and what we consider some basic rules to make your visit an agreeable experience for everyone.
Before you join the channel, and if you haven't already done so, please take a look at Wiibrew FAQ and Homebrew status to get a general overview of the state of affairs. After you join the channel, please spend some time watching the subjects of conversation before joining in -- unless you're absolutely positive you have something novel to contribute.
Over the months of Wii homebrew developments, #wiidev has become a high-traffic channel with more than 250 users at any time given. Please understand that we have to set up a few guidelines, and that we are willing to enforce them if necessary.
The good: What #wiidev is for
The point of #wiidev is to bring together people who have an interest in -- and ability to -- help further homebrew development on the Wii platform.
The language used on #wiidev is English. If you want to talk to someone in another language, please do it in a private message or another channel. As a channel for international information exchange, everyone benefits from using the same language.
The bad: What #wiidev is not for
- User support for homebrew software, games, or tools. While you may be able to run across homebrew developers in #wiidev, it is not a support forum where everyone is supposed to help you. A much more appropriate place to ask for support regarding a specific application is the discussion page of its entry here in the Wiibrew wiki.
- Speculation: We do not discuss what evil secret plans Nintendo may have, or other conspiration theories for that reason.
- Wishlists: We don't particularly care about sentences beginning with "I wish there was", simply because most of the times it means "please create this for me". The tools and the info are there -- if you want it to be done, do it yourself.
- Release dates: No developer in his or her right mind will tell you a release date, and we don't know about Nintendo's release schedule. Questions regarding release dates are really pointless.
- Sharing code examples -- use one of the ubiquituous paste web sites, and state its URL instead.
- General chit-chat, related to Wii or not. This means: No funny Youtube clips, no cool web sites, no discussion about the latest games, no semi-retarded internet memes. You will see random chat topics come up in conversation amongst regulars, but this is by no means an indicator that you may do the same.
The above topics are discouraged on #wiidev. There's a much better place for this: Join #wiidevot on EFNet for all your off-topic needs.
And the ugly: What will not be tolerated
The #wiidev ops can and will enforce kicks and bans for talk about what we consider downright bad for the homebrew community, such as
- Copyright infringement: Warez, VC, and WiiWare piracy. This includes talk about "backups", regardless of their legality, and tools related to piracy. Yes, that includes modchips.
- Copyrighted content: encryption and signing keys, Nintendo's own SDK, game resource files
- Playing IRC games: We have our own bots and our own scripts, do not bring yours along. Don't overtly announce your reason for being away, what song you are listening to, or other irrelevant info. And don't use an auto-rejoin script -- kicks are not intended just to test your scripts.
- Advertisement: no announcing of web sites or channels.
As a general rule, channel operators do not have to justify their decision to kick and/or ban you. They have been endowed with these powers and are trusted to judge whether they are necessary. If you have been kicked and/or banned, it's your fault, not the operator's.
You know how it is. Some questions come up over and over again. And while they are perfectly valid, answering them would clutter the channel. If you have been referred to this document, please understand that this is for everyone's benefit and not to shut you up.
If you have a question that is not answered here, feel free to ask it in the discussion of this page.
Hi, I can't code/reverse engineer/test but I would like to help, what can I do?
You are very welcome to hang around and watch the events, as long as you don't participate in off-topic talk (see above).
Hey, I have this really great idea ...
Even though chances are good someone else already had it, you are very welcome to grab the necessary tools and implement it. If you are looking for a coder to carry out your idea, be sensible about it. Most coders have their own plan, although some might be susceptible to constructive input.
I have a cool Wiimote/Glovepie script/tool/program
Yes, we know there are many nifty things you can do with the input it provides, but this is Wii development. Unless you can make it provide MORE input, do not mention it on #wiidev.
Does homebrew run yet?
Yes. Have a look at the Homebrew status for more info.
How can I do ... on Wii?
Please read the manual, or search the net. This channel is meant to be used to discuss Wii development, not everything relating to the Wii.
Is it possible to launch Gamecube software/homebrew on the Wii using Wii homebrew methods?
No, its not. It might be possible in the future, but its more likely Wii-specific versions of the Homebrew will be released long before that.
Is it possible to make an isoloader?
We do not discuss topics related to copyright infringement, please refrain from asking.
Can you help me with this emulator?
We do not discuss topics related emulators, please refrain from asking.
Really want to help? Become an Editor!
Help is always needed here on the wiki! Check out how to contribute.