Thread Naming Guidelines -*READ*-

Points of Required Attention™

Please chime in on a proposed restructuring of the ROM hacking sections.

04-24-24 09:16 PM

Guest: Register | Login

0 users currently in The Landfill | 3 guests

Main - The Landfill - Thread Naming Guidelines -*READ*-

New thread | Thread closed

Sukasa

Posted on 08-16-08 04:13 AM

Link | Quote | ID: 89017

Red Birdo
Level: 92

Posts: 880/2112
EXP: 7688404
Next: 68533

Since: 02-19-07

Last post: 4446 days
Last view: 3218 days

Since this did work once before on Incarnation two, I'm going to use Juggling Joker's old method here frmo SMW hacking.

OKAY, LISTEN UP!

If you're going to make a thread here, try and add the following into the thread title as needed, so that it's a little easier to sort out the morass of threads that are going to inevitably sprout up.

[56K] - If the thread contains or is likely to contain a large number of images or youtubes, add this to the thread to try and warn people with slower connections

[HOWTO] - Got a great tutorial? Add this to the thread name! If enough [HOWTO]s get posted, then a thread with links to all of them may become possible!

[QUESTION] - Need help with something a little too advanced for the help thread? Add this to the thread title!

[RELEASE] - This should really be obvious.

[DEMO] - This too- got a demo link? Post this.

[SS],[VIDEO] - Again, if you have screenshots or videos, tag the thread with these!

[SUGGESTION] Got a suggestion for the SMRPG forum? Add this to the thread name!

[ASM] - If the thread contains code or is programming-related, add this to the thread title.

EXAMPLES:

Mario's Wild Ride [SS] [RELEASE] - Someone made a game, released it, and tagged the thread that there were screenshots and a link to the ips.

Making Mario jump differently [ASM] [QUESTION] - The thread title says it all.

Got any other tag ideas? Post Them!

Main - The Landfill - Thread Naming Guidelines -*READ*-

New thread | Thread closed

Page rendered in 0.018 seconds. (321KB of memory used)
MySQL - queries: 37, rows: 46/47, time: 0.015 seconds.