[EXAMPLE] Plugin request formatting [FORMATTED]

This post is now outdated and replaced by the below link:
http://forums.bukkit.org/threads/read-me-first-plugin-requests-guide.81209/

Plugin category: EXAMPLE

Suggested name: ExamplePlugin

A bit about me: I'm a plugin dev who frequents plugin requests looking for good ideas, or a good cause, or just the offer of a bit of pizza (I do love pizza) and wanted to make an example of how to properly format a plugin request post. Don't ask me what plugins I've created, no really, don't.

What I want: I'd like to see perhaps properly formatted posts, or at least an attempt beyond the average all caps scrawl that has come to dominate this forum.
What people need to learn is that it's much easier to read a nicely formatted post, even if it's a bit longer than it needs to be, you can easily identify key points via proper formatting.
Also: skim-reading much easier with paragraphs! As an idea - people who've read this and formatted their post accordingly can put [FORMATTED] in their post title, and people will know they've taken the extra time to make their post readable and give the relevant information out.

Ideas for commands: No commands needed for this plugin.

Ideas for permissions: This should be a default:true permission player.canread and set it to false if they can't read this post.

When I'd like it by: Yesterday, though obviously it'll take a while before anyone more than a few takes notice of this post, I'll keep bumping it.

Similar plugin requests: None.

Devs who might be interested in this: @TnT @ChrizC @codename_B (yes I tagged myself)

 

I like that layout, would be much easier for the devs. Maybe a section as well with example commands they would like and how permissions should be seperated, if they have a preference.

 

Added

 

Great idea @codename_B
Stickied.

 

Hrmm....
*ponders things*

 

Devs who might be interested in this:
<===
I hate posted which are created in 1 minute and your like good idea but NO IDEA WHAT YOU WANT!!!

 

Hopefully people use this, I don't like posts that are like:

"Can I haz a plugin request? I need this done and that done. Contact me on skype."

 

So, what plugins have you created?

 

Did you get your username changed?

 

@Daniel Heppner
Yup. Decided to change it so as to remove the sexual innuendo.

Don't want to come off as a 12 year old who still giggles at sex puns.

 

Devs who might be interested in this:
I'm just starting with some plugins so if it's not too complicated (like a full blown permission mod) you can tag me too!

 

Really what was your name then? I didnt see anything wrong with it

 

@thehutch
Just look at the Dev.Bukkit name for reference.

 

It took me like 10 minutes to figure that out.

 

Here's a empty version to copy paste if people want it.

Code:

[b]Plugin category:[/b]
 
 
[b]Suggested name:[/b]
 
 
[b]A bit about me:[/b]
 
 
[b]What I want:[/b]
 
 
[b]Ideas for commands:[/b]
 
 
[b]Ideas for permissions:[/b]
 
 
[b]When I'd like it by:[/b]
 
 
[b]Similar plugin requests:[/b]
 
 
[b]Devs who might be interested in this:[/b]
 

 

I recommend the addition of a Contact Me Here:
section.

 

What's wrong with PMs?

 

Just incase they want to talk over Skype, or have a TeamSpeak for multiple devs etc..

 

Wouldn't you ask for this information over a PM if you're interested?
Also, please quote me when you are replying to me.

 

Yes, you could, I was just thinking the OP could try to get all important information into the post as simply as possible, so that the plugin could get started with as least setbacks as possible.

 

can you remake hero brine

 

@codename_B

As a suggestion to the plugin request format, I think it'd be a lot easier to sort through if there was a formatted title, like the plugin submissions.

So the title of the thread would look like:
[MECH/ADMN] Plugin Example Title - Brief Description [$$]
(The money title would be if they're willing to pay, possibly have something like [$10], and have it not included if they're planning on not paying for it.)

 

Love this, thanks codename_b

 

codename_B Maybe adding a "Do you want it public or private:" field could be nice

 

will the plugin i REX be public or send to me?
i just asking bekos i have somse ideas to public plugins
but if i just get the made plugins send to me do i so have permissions to do it public?

 

"rex"? "bekos"? -.-

Chances are...public will be someone who volunteers but if you are paying for a plugin then it'd be your choice to make it public or keep it private. It will between you and the dev.

 

sorry for my bad english and the REX shull be REQ my bad

 

Lol, s'okay...I'm a bit of a grammar punk.

 

removed the "willing to pay" bits, see rule 5.

 

why? why is this needed..?