Register - Login
Views: 99376559
 Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users
Ranks - Rules/FAQ - Stats - Latest Posts - Color Chart - Smilies		 04-23-22 09:21:07 PM
Jul - NO! GO TO STAR! - Guidelines (read first) New poll - New thread - Thread closed
Next newer thread | Next older thread
Kles

Level: 87


Posts: 857/1947
EXP: 6306411
For next: 86363

Since: 07-23-07


Since last post: 68 days
Last activity: 12 hours
Posted on 10-07-07 11:59:02 AM Link
I'm copying this over from the SM64 forum (with a few changes here and there) so we can have some ground rules here. They're pretty universal. I believe this community will be more mature than the SM64 one, but there will always be those who just don't get it.

FAQs

Before you ask ANY QUESTIONS, please read the forum FAQ. There are few things more annoying than being asked the most mundane, half-way obvious and easily answered questions over, and over, and over by someone who didn't have the courtesy to read the FAQ.

ROM POLICY

Direct linking to any commercial* ROM, be it the vanilla game or a hacked version, is expressly forbidden. IPS/NINJA/PPF patches are okay. However, what you do in private is none of our business.

*Commercial refers to a ROM that was dumped from a video game that was released on a console for profit. Homebrew ROMs, meaning that they were made by amateur programmers who are coding for the system for non-profit reasons, are perfectly fine to link.

HOW TO GET HELP

If you've read the FAQs and help thread and you still have questions, post a reply to the help thread with clear and concise information on your problem. If you post a question simply saying "I open the program and it crash what do I do" - you will probably get no help at all. We're not mind readers, we can't know exactly what the issue is. If you need help on a feature, be specific on what you need to be done. If you're having technical issues, be very specific. If the program is behaving oddly, note very specifically what is going wrong ("it turns black" is NOT specific at all). If the program is crashing or failing to start up, post exactly what the error message says, along with system specs. The more in depth you explain your problems, the greater your chances of being helped.

DON'T BE AN IDIOT

This should be common sense, but I'm going to throw this down for consistency. First off, type reasonably well. "hey wen u open th rom ware do i find how2 chang tihng?s" is absolutely unacceptable. If English is not your native language, there will be much more leniency for you. Still, don't use it as an excuse to not make sense. You don't need to be completely perfect by any means, but at least give an effort.

Another part of not being an idiot is being reasonably nice to people. Don't be rude. If a newbie comes along and violates everything I've said in this thread, please don't just roast them on the spot. Instead, just give them a friendly link to this FAQ and leave it at that. If you jump all over them with a series of personal attacks and general flaming, you may quickly find yourself being the one in trouble. If a person repeatedly violates the rules, don't play moderator; let someone who IS a moderator/admin take care of the situation.

PUNISHMENT AND ENFORCEMENT

All rules are usually enforced. The punishment for breaking the rules generally goes as follows:

First offence: warning
Second offence: three day ban
Third offence: week long ban
Fourth offence: indefinite ban

This is not set in stone and in varies per situation. More often than not, if the staff believes you're not getting it after the second (or sometimes even first) offence, they won't hesistate to skip right to the indefinite ban.

CONCLUSION

Don't be intimidated by this FAQ! It's actually not that complicated. In summary:

Read the FAQ
Don't post ROM links
Type reasonably well
Don't be a jerk

That's all you really need to know!

FOOTNOTE

While it's no means a rule, if you want people to try out your hack, post screenshots. Seriously. It's the most important thing.

____________________
( ﾟ³ﾟ)三№♥
Next newer thread | Next older thread
Jul - NO! GO TO STAR! - Guidelines (read first) New poll - New thread - Thread closed


Rusted Logic
Acmlmboard - commit 47be4dc [2021-08-23]
©2000-2022 Acmlm, Xkeeper, Kaito Sinclaire, et al.

28 database queries.
Query execution time:  0.084990 seconds
Script execution time:  0.008013 seconds
Total render time:  0.093003 seconds


TidyHTML vomit below
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 2 column 300 - Warning: unescaped & or unknown entity "&page"
line 119 column 11 - Warning: <form> isn't allowed in <table> elements
line 118 column 10 - Info: <table> previously mentioned
line 120 column 11 - Warning: missing <tr>
line 120 column 119 - Warning: missing </font> before </td>
line 124 column 16 - Warning: plain text isn't allowed in <tr> elements
line 120 column 11 - Info: <tr> previously mentioned
line 125 column 68 - Warning: missing </nobr> before </td>
line 141 column 68 - Warning: missing </nobr> before <tr>
line 147 column 35 - Warning: missing <tr>
line 147 column 50 - Warning: missing </font> before </td>
line 148 column 37 - Warning: unescaped & or unknown entity "&id"
line 147 column 187 - Warning: missing </font> before </table>
line 149 column 35 - Warning: missing <tr>
line 149 column 50 - Warning: missing </font> before </td>
line 149 column 91 - Warning: missing </font> before </table>
line 156 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 158 column 9 - Warning: missing <tr>
line 176 column 13 - Warning: missing <tr>
line 179 column 73 - Warning: <style> isn't allowed in <td> elements
line 179 column 9 - Info: <td> previously mentioned
line 225 column 7583 - Error: <z> is not recognized!
line 225 column 7583 - Warning: discarding unexpected <z>
line 228 column 17 - Warning: missing <tr>
line 228 column 17 - Warning: discarding unexpected <table>
line 231 column 35 - Warning: missing <tr>
line 231 column 50 - Warning: missing </font> before </td>
line 231 column 91 - Warning: missing </font> before </table>
line 233 column 35 - Warning: missing <tr>
line 233 column 50 - Warning: missing </font> before </td>
line 234 column 37 - Warning: unescaped & or unknown entity "&id"
line 233 column 187 - Warning: missing </font> before </table>
line 235 column 17 - Warning: discarding unexpected </textarea>
line 235 column 28 - Warning: discarding unexpected </form>
line 235 column 35 - Warning: discarding unexpected </embed>
line 235 column 43 - Warning: discarding unexpected </noembed>
line 235 column 53 - Warning: discarding unexpected </noscript>
line 235 column 64 - Warning: discarding unexpected </noembed>
line 235 column 74 - Warning: discarding unexpected </embed>
line 235 column 82 - Warning: discarding unexpected </table>
line 235 column 90 - Warning: discarding unexpected </table>
line 237 column 9 - Warning: missing </font> before <table>
line 249 column 25 - Warning: discarding unexpected </font>
line 258 column 37 - Warning: discarding unexpected </font>
line 236 column 1 - Warning: missing </center>
line 120 column 63 - Warning: <img> lacks "alt" attribute
line 125 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 125 column 93 - Warning: <img> lacks "alt" attribute
line 141 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 141 column 98 - Warning: <img> lacks "alt" attribute
line 148 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 216 - Warning: <img> proprietary attribute value "absmiddle"
line 161 column 22 - Warning: <img> lacks "alt" attribute
line 161 column 63 - Warning: <img> lacks "alt" attribute
line 161 column 112 - Warning: <img> lacks "alt" attribute
line 161 column 162 - Warning: <img> lacks "alt" attribute
line 162 column 11 - Warning: <img> lacks "alt" attribute
line 172 column 15 - Warning: <img> lacks "alt" attribute
line 179 column 3683 - Warning: <img> proprietary attribute value "absmiddle"
line 179 column 3683 - Warning: <img> lacks "alt" attribute
line 187 column 4311 - Warning: <img> proprietary attribute value "absmiddle"
line 187 column 4311 - Warning: <img> lacks "alt" attribute
line 234 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 234 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 234 column 216 - Warning: <img> proprietary attribute value "absmiddle"
line 243 column 25 - Warning: <img> lacks "alt" attribute
line 248 column 267 - Warning: <img> lacks "alt" attribute
line 149 column 50 - Warning: trimming empty <font>
line 228 column 17 - Warning: trimming empty <tr>
line 231 column 50 - Warning: trimming empty <font>
line 125 column 68 - Warning: <nobr> is not approved by W3C
line 141 column 68 - Warning: <nobr> is not approved by W3C
line 177 column 27 - Warning: <nobr> is not approved by W3C
Info: Document content looks like HTML5
Info: No system identifier in emitted doctype
Tidy found 71 warnings and 1 error!

The alt attribute should be used to give a short description
of an image; longer descriptions should be given with the
longdesc attribute which takes a URL linked to the description.
These measures are needed for people using non-graphical browsers.

For further advice on how to make your pages accessible
see http://www.w3.org/WAI/GL.
You are recommended to use CSS to specify the font and
properties such as its size and color. This will reduce
the size of HTML files and make them easier to maintain
compared with using <FONT> elements.

You are recommended to use CSS to control line wrapping.
Use "white-space: nowrap" to inhibit wrapping in place
of inserting <NOBR>...</NOBR> into the markup.

About HTML Tidy: https://github.com/htacg/tidy-html5
Bug reports and comments: https://github.com/htacg/tidy-html5/issues
Official mailing list: https://lists.w3.org/Archives/Public/public-htacg/
Latest HTML specification: http://dev.w3.org/html5/spec-author-view/
Validate your HTML documents: http://validator.w3.org/nu/
Lobby your company to join the W3C: http://www.w3.org/Consortium

Do you speak a language other than English, or a different variant of
English? Consider helping us to localize HTML Tidy. For details please see
https://github.com/htacg/tidy-html5/blob/master/README/LOCALIZE.md