Before you start to make a guide
1) If you are doing an update to a guide... state "I am doing an update to the xxx guide" at the beginning of your guide, and maybe give an example of what is being updated.
That should stop the nay-sayers...
Merchant Quest update I did... the thread has been removed but... I kinda yelled at DSOFA for starting a new guide, then he showed me examples of what had changed, Now the updates have been added.
The adventure alliance guide... I knew from the posters last log in date that no updates were going to happen so I finished it.
but I GAVE HIM CREDIT for the original in my guide! (up front so others wouldn't complain)
(original moved to reserve guides)
2) Ask the forums if a guide has been done before... maybe ask twice to be sure.
Give it a few days for all responses - not everyone reads the forums every day.
3) Most of the old info is out there... just not in one place.
again ask for links... then state that your guide is putting info together for some reason...
4) to keep others from posting the same right before you do..... post a partial guide!
Let others know what you are doing so they don't duplicate your work! Guides can take months to put together.... post updates/edits frequently. (need I say post in the same thread?)...
USE THE EDIT FUNCTION to update already written items or edit your reserved spaces.
[ I can not guarantee this will stop others from posting.... I remember one guide in particular where it was being updated daily as fast as we could throw the new info at the poster/editor, but someone else got all the info together (possibly from the Chinese server) and got it posted before the guide was done... that was rather disappointing seeing her work "wasted" like that.... he just never looked to see if anyone else was doing a guide...no circumventing that]
5) To keep all the info together with out anyone commenting in between:
--> PLEASE DO THIS otherwise your guide is almost useless.
Make multiple replies to your post ahead of time... you just need to put 20 or so characters in each post... I generally put : "reserved for future updates" in each "blank" reply. Don't be afraid to post too many "reserved posts". you can always delete them later.
*hint* using color text and or bold/italic underline or sized font uses up more space. Each post is restricted to 10,000 bytes,
so add a few extra "reserved" posts if you are going to use color, esp if you type it in regular text then edit the colors in. (click "check length" in the editor to see how big your post is).
How To Submit a guide:
Post it to the General Discussion so that all Mods will see it.
You can not post directly to the Tutorials and Guides section. A moderator must insure that a similar guide does not exist or that the one you are submitting is superior in quality and relevancy (updated).
Then It will be moved to the proper guide section and a link will be added to the list of guides.
How to write a good guide - by multigameer
The reason I'm making this is because Voyage Century is a great game with great gameplay but unfortunately the gameplay can be confusing and new players need guides. I noticed some of the current guides are decent with most information included but not written as well thus taking more time to read the entire guide to find something. Hopefully this guide can help new guide writers to make easier to read guides.
-Before you Start
-Starting a Guide
- Parts of a Guide
- Forum Codes
-Examples of Good/Bad Guides
- Before you Start
When you are planning to write a guide, make sure the guide you are writing is needed. and/or other guides of the subject are outdated and you are not creating a guide just for your karma gain. You would also need to have an in-depth knowledge and/or experience of the subject you are planning to write. An inaccurate guide is simply a waste of time for both the writer and reader.
- Starting a Guide
To begin your guide, you should write an introduction of your guide and the things you will be explaining in your guide to catch the readers' attention.
Parts of a Guide:
In any well written guides, you should ALWAYS use proper grammar and spelling (avoid slangs). Keep in mind that a guide should be like a newspaper (in my opinion). You should to keep everything in order from the beginning to the end with the most important facts to the top of each section and less important details to the bottom of each section.
- Visual Aids
Anything other than text are probably the most eye catching parts of guides since explaining can be hard without visual aids. Pictures/Maps should be used to explain. Tables should be used as comparisons for your explanations. You can either upload attachments or use another image host and link your images. Personally, I dislike guides using image hosts that only provide a thumbnail version of the original image and you would have to open a new window/tab to view it.
In your guide, you should provide viewers with further reference to the subject.
Organizing is key to a good guide so use a table of contents! Use color coded sections if you need to but you should NEVER use hard to read colors such as yellow or pink. Dividing into chapters like a book is also useful (section 1.1-1.9 2.1-2.9 etc). Anther technique is to give each section a special code ([A001]-[F009] etc) if your guide is long so people can just press Ctrl+F and find the section they need.
This is the hardest element of a good guide. You need to throughly explain the subject to avoid questions. You need to be as accurate and detailed as possible. If you left something out and somebody asked about it, you should get it fixed/added immediately. You can also try getting one of your friends to read your guide and see if they can understand it without playing the game.
- Training Method
If your guide explains about a skill, you should give a detailed list of locations/methods of training that skill. Divide each section by the skill level (Lv1-10 Early Training... Lv11-40 Mid-Level Training... Lv41+ High-Level Training etc) is very effective. Give additional hints, alternative methods, and ratings (cost to level, speed of leveling, overall rank etc) separate an excellent guide from a decent guide. Pictures and tables are crucial to be effective.
Give examples of the subject your are writing about encourages readers to actually try your guide instead of just read it and forgetting it 5 minutes later. Videos and pictures or yourself or others are very encouraging.
To end your guide, you should write an overall conclusion and maybe an overview of everything (simplified version).
Forum Editor Functions:
- 1. (this area no longer shows when posting in the General Discussion section)
- 2. Your guide name; make it short and simple ("Guide" instead of "@@@@@GUIDE!!!!@@@@@").
- 3. Make text bold (good for titles or important terms).
- 4. Make text italic (good for special terms).
- 5. Make text underlined (good for titles or important terms).
- 6. Change your font type (Arial, Times New Roman etc.); DON'T USE FANCY FONT because it's hard to read.
- 7. Change font size (good for titles); smaller font size for subtitles and bigger font for main sections
- 8. Change font colour; DON'T USE LIGHT COLOURS because it hurts the eyes and impossible to read.
- 9. Adds a link (to link your references etc.)
- 10. Adds a picture (good guides need visual aids).
- 11. Adds lists (left is numbered and right is bullets).
- 12. Standard Editing Mode.
- 13. Visual Editing Mode (for making tables, refer to next section).
How to Make a Table:
Go to WYSIWYG mode in editing (13 from above section). Next press the button highlighted in red. You will see this next:
Enter the number of rows and columns you want (rows is horizontal and columns is vertical). Then the width and background colors too.
In the Width box you can enter a percentage up to 99%
This will set the table with on all screens of all sizes.
99% will fill the width of all screens
75% will use 75% of the screen width measured from the left
25% uses 25% etc etc...
You can use BB code instead of the icons to make tables and select colors.
BB code is similar in structure to HTML but is NOT the same.
HTML is a programming language, BB code is recognized by the Discuz! Program.
BB code was invented ( a few years before the Discuz! program) because if HTML were allowed people could program Trojans, harvesting programs and other malicious items into discussion forums.
Forum BB Codes
The following codes work in the Voyage Century Forum (yes there are plenty of other BB codes but only these will work in THIS forum)
|Name & Syntax||Example of what it does|
|Font Size; (use # = 1- 7)||text (size 5 shown)|
|Font Color;||text (blue shown)|
|Left Align Text;|
|Right Align Text;|
|Link (named);||VCO web site|
|Image or picture;||note size is 34x34 pixels, the size it was created as.|
|Image resized;||note size is 50x85 pixels|
|Hide with limits[code][hide=10000]text2[/hide][/code]||[hide=10000]text2[/hide]|
Note that the code is easier to read if written as below
HOWEVER after you submit the thread, and attempt to edit it, it will show as in the first example.
Things to know
Black text is the default setting. So you do not need to code in black text unless it is in between a text line of a different color:
Example 1; Black > Red > black text
This is a TEST this is only a test.
code looks like;
Example 2; Red > black > red text
This is a 2nd TEST this is only a test.
code looks like;
Example 3: Red > black > Red
This is a 3rd TEST this is only a test
code looks like;
Default text size is 2 in Firefox and Internet Explorer but is size 1 in Opera.
Test example of text size 1, text size 2, text size 3 text size 4 and back to default size.
code if interested:
Spacing is often thrown off when submitting a thread.
ALWAYS re-read your post then go back and edit any "mistakes"
The Letters used for designating a color are the standard HTML Hexadecimal numbers.
Most computers in 2014 can display about 16,000 different colors... though with Hexadecimal there are 16.000.000 possibilities.
In the 80s and 90s computers had a standard pallet of 216 "web safe colors" and reserved 40 as standard fixed system colors.
Those are the 40 colors you see in the pull down of the edit menu.
I can not add an outside link, but search "hexadecimal color chart" if you wish to learn how to write the color codes.
You can not add pictures if you use the Firefox browser. This is due to a problem with the forum coding. This will not be fixed.
I have to now switch between Firefox and Opera to fully write a guide. (problem fixed in 2015)
- Examples of Good/Bad Guides
-Tortuga - A Complete Guide
-Storyline / Scenario Quests (great information but badly organized and takes awhile to find what you need)
- Extra Notes
-This is basically a guideline or tips of how to write a good guide.
-Please don't be offended if I listed your guide in the bad guides section.
-Keep your guides updated!
-Use Excel or other organizing programs if you plan to make a big table of data and take a screenshot or two.
-Save a backup copy just in case.
- Extra Notes
[ Last edited by xanthian31 at 2015-12-6 11:09 ]