- Joined
- Oct 20, 2013
- Messages
- 846
- Reaction score
- 1,295
- Points
- 0
Many of us know the threads I'm talking about. The threads in Feature and Idea Discussion that are, quite simply, "I think x should be implemented because y i would use it a lot." Threads like these give no real support to your idea, and if anything, make it less likely to get accepted. Yes, an idea can be expanded upon in the comments, but the main meat of any argument should be in the main body. Here is a guide on how to make a proper suggestion thread.
Plugin/ Mod Suggestions:
Race Suggestions:
Lore Suggestions:
Building/ Location Suggestions:
That is about it. Keep these in mind when suggestion in the future, and have a very Massive day!
Plugin/ Mod Suggestions:
These are some of the more common threads I see. Often, these are some people's first threads. All too often, I see a one paragraph description of the idea, or even worse, one sentence. Something like this is way too short to convey your idea in any manner.
A plugin suggestion should consist of the following in an order somewhat similar to this:
A plugin suggestion should consist of the following in an order somewhat similar to this:
- A brief description of the plugin.
- A more in depth description, going into specifics of how it would work, what it would do, and the limitations of it.
- Why such a plugin is needed. What is the benefit to the community as a whole. Does it benefit you and you alone? Does it benefit the server as a whole, or at least a large community? If it is for your benefit alone, don't post it.
- What are some drawbacks to such a plugin? Don't ever just praise an idea to no end. to make yourself seem more credible, do post some negatives that such a plugin could cause. There is nothing worse then a plugin being extremely buggy or broken when it is installed on the server. Do post any possible suggestions on how to fix these.
- Post some links pertaining to this plugin. Is there already one in existence? Are there similar plugins? These greatly increase the likelihood of your idea being approved. Don't suggest something that'll waste the staff's time.
- A pole. This gives an overall feel of the communities opinion. Never rig the pole, and give more then two answers. Three is okay. For is good. Five or six is idea. More then that could be overkill. Kill middle-ground options, and neutral options. Opinions aren't just one side or the other. There are many who are in-between.
- Never suggest a game changing mod like the Aether, Mo'Creatures, Metallurgy, Thaumcraft, or similar mods. These will never be implemented, as not everyone can run mods. This would merely limit the community for Massivecraft. Instead, suggest mods like More Player Models or Optifine, where they have little effect on the gameplay, are completely client-side, and give no unfair advantage.
- Don't suggest plugins that have a large number of moving blocks. Plugins like Movecraft or Bending, while cool, would stress the servers even more then some of them already are. This would only lead to crashes, and the server being a laggy mess.
- Don't have a suggestion shorter then three paragraphs. They should also be easy to read and follow. Each sentence should flow into the next, and each new idea should transition. Each paragraph should also pertain to one idea. Stay on task. Check for spelling, punctuation, grammar, homophone, and structuring errors. If English isn't your native language, or if you are very young, Type the thread in Microsoft Word. This will be able to point out errors and help your fix them. Read things out loud to make sure they make sense.
- Don't ever make two suggestions in a single thread. Each idea should have its own thread, so as to avoid confusion, and to keep it organized. It is easier to follow each topic if they are on separate threads.
Race Suggestions:
Race suggestions are not being taken currently, and probably won't be for a while, if ever. However, if you insist on suggestion one, make it high quality. It may be implemented as an extinct race, or even as a species of animal. Race suggestions should contain:
- Brief description of the appearance of the race and their culture. This can be expanded upon later.
- Lore of the race. This can either be in depth of very minimalistic. It doesn't matter. More in depth lore can flesh out the race even more, but it is very unlikely to be accepted in the state presented, and would probably be overhauled.
- Include any subraces, if any. Describe each, and how they differ from other members of the race.
- Their culture. Like the lore, you can go in depth or very shallow. It's up to you.
Lore Suggestions:
Lore should be kept in the Write-me-Lore section. Follow the steps given there in the Read-me for the section, and you should be good. As always, go in depth. Unlike the race suggestions mentioned before, lore pages are welcomed with open arms, quite often, and will be worked on similar to Character Creation. Depth is key. Shallow details in the lore is frowned upon. Take any suggestions given to you by staff and add them or remove them. Staff won't accept something they won't like.
Building/ Location Suggestions:
When suggesting a location for Regaila, the size of the thread depends on the size of what your are suggesting. Give a detailed description of the building. What will it be used for? What will it look like? What will be inside of it? Outside of it? Why is it needed? Ask questions like these, and organize accordingly. Details are important. Remember, suggesting a location for your character and your character alone to sit around and watch TV won't get accepted, but something like a public recreational facility might be. Just remember, the World Staff have an agenda, and a Regalia V3 to build.
That is about it. Keep these in mind when suggestion in the future, and have a very Massive day!