Editing POTCO — Disneys Online Worlds

POTCO

Discussion about the wiki or on wiki topics can be found at:

Pirates Online Forums "Disney's Online World Guide" forum

Enemy Templates

What it looks like

This template is used to show information about POTCO's enemies.

Back to Previous Page

Enemy Name

What you type

<noinclude>
{{POTCOEnemies
|PrevPage=[[Previous Page]]
|Name=Enemy Name
|Levels=Levels
|HPs=Hit Points
|Attacks=Attacks
|Locations=Location
|Notes=Info <br>
Info <br>
Info

|Image=Image link here.
}}
</noinclude>

What it looks like	What you type
If the enemy is part of the Navy, show this using: This enemy is part of the Navy.	{{EnemyNavy}}
If the enemy is part of the EITC, show this using: This enemy is part of the EITC	{{EnemyEITC}}
If the enemy is an animal, show this using: This enemy is part of the Animals group	{{Animal}}
If the enemy is a plant, show this using: This enemy is part of the Plants group	{{Plant}}
If the enemy is part of Jolly Roger's Army show this using: This enemy is part of Jolly Roger's Army.	{{JollyRoger'sArmy}}
If the enemy is a boss show this using: This enemy is a Boss.	{{Boss}}
If you want to show what levels an enemy can be, show this using: Levels: nums	{{levels\|num-num}}
You can show the enemy's HP range using: Hit Points: nums	{{HitPoints\|num-num}}
If the enemy is a boss, you can show the type of enemy they are using: This boss is a(n) Enemy Type.	{{BossEnemyType\|[[Enemy Name]]}}

Quest Templates

What it looks like

What you type

This is used to show information about POTCO's quests.

Name	Task	Description	Reward	Spoiler/Notes	Picture

<noinclude>
{{POTCOQuestHeader}}
</noinclude>
|-
|
|
|
|
|
|
<noinclude>
{{POTCOQuestFooter}}
[[Category:POTCO Quests]]
</noinclude>

If a quest gives out Notoriety, show this using:

num Notoriety Points

{{Notoriety|num}}

If a quest page is not yet complete, show this using:

'The various quest tasks/steps listed here represent {{#ifeq: +}} of this quest.

{{{POTCOQuestStub}}

NPC Templates

What it looks like

What you type

This is used to show information about POTCO's NPCs.

Name	Location	Job	Quests	Image
Person's Name	What island the person's on	What their job is (gypsy, blacksmith, etc.)	Link to page(s)	Link to image

<noinclude>
{{PNPCTableHeader}}
</noinclude>
{{PNPC
|name=Person's Name
|location=What island the person's on
|job=What their job is (gypsy, blacksmith, etc.)
|quests=Link to page(s)
|image=Link to image
}}
<noinclude>
{{PNPCTableFooter}}
[[Category:POTCO NPCs]]
</noinclude>

If the NPC is a gypsy, show using this:

This person is a gypsy.

{{gypsy}}

If the NPC works at the docks show using this:

This person works at the docks.

{{dock'sMan}}

If the NPC is just a towns person, all they do is give out quests, show using this:

This person is a towns person.

{{townsPerson}}

If the NPC is a gunsmith, show using this:

This person is a gunsmith.

{{gunsmith}}

If the NPC is a blacksmith, show using this:

This person is a blacksmith.

{{blacksmith}}

If the NPC is a grave digger, show using this:

This person is a grave digger.

{{GraveDigger}}

If the NPC is a jeweler, show using this:

This person is a jeweler.

{{jeweler}}

If the NPC is a doctor, show using this:

This person is a doctor.

{{doctor}}

If the NPC is a bartender, show using this:

This person is a bartender.

{{bartender}}

If the NPC is a shipwright, show using this:

This person is a shipwright.

{{shipwright}}

If the NPC is a tattooist, show using this:

This person is a tattoo artist.

{{tattooist}}

If the NPC is a trainer, show using this:

This person is a trainer.

{{trainer}}

Ship Template

What it looks like

What you type

This is used to show information on enemy ships in POTCO.

Name	Type	Levels	Group	Image
Name of the ship.	Type of ship.	Show Levels	State the group it's in	Link to image

<noinclude>
{{EnemyShipTableHeader}}
</noinclude>
{{EnemyShip
|name=Name of the ship.
|type=Type of ship.
|levels=Show Levels
|group=State the group it's in
|image=Link to image
}}<noinclude>
{{EnemyShipTableFooter}}
[[Category:Enemy Ships]]
</noinclude>

This is used to show that ships are part of the Navy:
This ship is part of the Navy

{{ShipNavy}}

This is used to show that ships are part of the EITC:
This ship is part of the EITC

{{ShipEITC}}

This is used to show that ships are part of Jolly Roger's Army:
This ship is part of Jolly Roger's Army

{{GhostShip}}

Gold Template

What it looks like	What you type
If you want to show how much something is in gold, show using this: Gnum	{{goldPrice\|num}}

TODO Templates

What it looks like	What you type
To leave a comment on a page about something that needs to be done (and also have the page in :Category:TODO), use this: TODO: What needs to be done	{{todo\|What needs to be done}}
To show that there is no image available in a designated spot (and also have the page in :Category:TODO:Pictures), use this:	{{PImageNotAvailable}}
To show that some data is unknown for pirate stuff only (and also have the page in :Category:TODO:POTCO Unknown Data), use this: *Unknown*	{{punknown}}
If a page it too short and/or lacking too much information to use {{todo}}, use this (it must be a Pirates of the Caribbean Online page!): This Pirates of the Caribbean Online-related article is a stub. You can help the Disneys Online Worlds Wiki by [{{SERVER}}{{localurl::Editing POTCO}} expanding it].	{{PirateStub}}

Names: Quests and Files

Quest names: Quest names (and thier tasks) appear to consist of uppercase letters. For consistency, it is preferred that all uppercase letters be used, with the exception of the main page where the quests are listed. In the event a quest name or quest task name is duplicated, a number within paranthesis (making it separate from the quest/task name) should be placed at the end separated with a space. (Ex. VISIT GUNNER (1), VISIT GUNNER (2), etc)Filenames for Images: We collect, organize, and upload volumes of images for various quests in the game. If filenames are properly named, then they can easily be identified as far as exactly where they belong within the series of quests in the game. It can also improve searching of images providing the ability to search not only by the task name, but by the quest name, the sub-quest name, etc.
Example:
Task:

  Story Chapter: Black Pearl
     Second List
        Gunner
           Make Rum
              Make Grog
                  1 Fistful of mud

Filenames can be rather lengthly, so we can shorten them by abbreviating some more common parts of the tree.
The above example may be reflected in this manner in a filename:
BPQ_2ndList_Gunner_MakeRum_MakeGrog_1FistfulOfMud.jpg
BPQ = Black Pearl Quest, 2ndList = Second List, etc..
This allows us to know exactly where this image fits in the series, it also allows us to search for all images based on "BPQ", "2nd List", "Gunner", "Make Rum", "Make Grog", and "1 Fistful Of Mud", instead of just a typical "1 Fistful of mud.jpg".

Other

What it looks like	What you type
This is used to a Game Tip for POTCO (but only used from Game Tips seen on the official site): {\|		Game Tip: Insert The Tip Here

{{Game Tip|Insert The Tip Here}}

|- |To make a note, use this:

NOTE: note

{{note|Insert The Note Here}}

|- |To mark something that was released, use this:

Released:

{{released|Insert The Date Here}}

|- |To mark something that was retired, use this:

Retired:

{{retired|Insert The Date Here}}

|- |To mark something that was re-released, use this:

Re-released:

{{re-released|Insert The Date Here}}

Discussion community comments archived from Talk:Editing POTCO

File Names Of Quest Images

Should we not abbreviate the quest names, because if we really do want to search a certain part of the quest, we might not remember that we abbreviated it, which could make find it more difficult?

Also, since the quest names for the new clothing quests has 2 repeating quest names in the start of the quest, should we include both names? Here's an example:

1 PIRATE LIFE
* 1.1 PIRATE LIFE
* 1.2 PIRATE PLAY CARDS

(This is taken from a quest TOC page)

So, naming the picture would be:

PirateLife_PirateLife_PiratePlayCards.jpg

This may look like extra, but it is staying consistent with the quest file name. --Haveamagicalday (Talk | Contributions) 16:11, 29 August 2008 (PDT)

I would definately repeat/include both names in the side quests. I havent personally needed to do a search for images really, but understand the value in it. The main story quest in itself could create some very lengthly filenames. Perhaps using an acronym of sorts for the primary quest name/tier maybe helpful in this case. Knowing the possibility (and the fact its limited to story quests) should not hinder a search. --OFxZeppers 22:50, 2 September 2008 (PDT)

Should we have a list of abbreviations that could be used, so we all know of them, so it will be easier to search (if necessary)? --Haveamagicalday (Talk | Contributions) 17:04, 3 September 2008 (PDT)

Might be best to go ahead and NOT abbreviate or use acronyms, I thought that since it would be a real common portion of the filename abbeviations/acronyms might suffice. Any further discussion for using abbreviations/acronums vs complete names? If we go with using acronyms for common quest headers (ie story quest title), a list of terms/acronyms used would likely prove useful.--OFxZeppers 19:21, 4 September 2008 (PDT)

Well, I kind of like the idea as well with abbreviations (in some ways). If we do decide to do this, I think the best place to have a list of abbreviations would be on the talk page of that quest. So, if there are duplicate quest names, or there is a long line of quests that tab off from a quest, we could abbreviate them, and on the talk page of that quest, say what the abbreviation means. If we did this though, that would mean we would have to complete the entire quest before we could start uploading images, but we could add the info for the templates and quest pages, just without the image until everything is done in the game :)?

Any ideas/suggestions/comments? --Haveamagicalday (Talk | Contributions) 17:53, 5 September 2008 (PDT)

I would prefer to leave any abbeviations or acronyms limited to primary quest name, and perhaps in the case of the story quests, the next tier as well as they will be repeated often. I think that abbreviating the names for regular tasks with repetitive names would defeat the purpose and may complicate things. This would limit the need for a page listing the acronyms which may be listed on the POTCO help page.--OFxZeppers 11:36, 8 September 2008 (PDT)

Quest page formating

Ok, let's talk about the quest pages. I thought the way I had it was perfectly fine. It is clean and easy to read. Maybe this style will work well for just the smaller quests?

Now it runs into problems on the Black Pearl Quest. I just really hate the other way of doing it. It's unreadable to me other than it makes the TOC look nice.

Is there any way to make it not go too many levels deep? Maybe we can break it up differently so it doesn't need to.

Any other ideas? --Hile 16:25, 4 September 2008 (EDT)

For now, I would like to continue doing the quest I'm working in the format they are currently in until we come to a final decision on how we want to format the quest pages. Thanks. --Hile 15:53, 4 September 2008 (PDT)

I'm fine with having you continue to add quest pages in your current style at this point (really the information needs to take center stage, better to have slightly inconsistent format than missing information), but just be aware that depending on any decisions that are made, you might need to go back and reformat them. Hopefully we will be getting input from other editors soon.--UpInTheAir 16:02, 4 September 2008 (PDT)

I sent a reply to the message, but here's what I said mostly (shorter here). Is it possible that you, Up, could add more = (headers), so Hile's idea works, because that is a good idea, until you get into the really long quests like the Black Pearl one.

Should we use a __NOTOC__ first. Then, we can make our own, TOC, and link it to it's propper headers. This could possibly eliminate the problem with Hile's idea (format) :-)! We could also get rid of the numbers that the TOC would have (if we want to) :-)! Also, we could just use one set of headers (3 on each side of the quest name) for all quests (since we will have the TOC the way we want it)?

Any comments or ideas on this, or any other ideas on how we could fix this problem with formatting? --Haveamagicalday (Talk | Contributions) 17:47, 4 September 2008 (PDT)

Ok, I'll throw in my 2 cents. If you view the wiki page in a window, and not fullscreen (like many do, playing the game in a window with the browser open for information.) then this new method that is basically creating a single table with all the steps in it, can be hard to follow. The single table method resizes the table with the browser windows resizing often making the columns of information narrow with a great deal of information on them (2-3 sentences take half a page). They also then run together into the next step if one doesnt pay attention to the cell boundary line which is not much, the information continues on with no 'division'. Here are some links that reflect what im referring to.

New: http://pirates.teamofx.us/ss/wiki/quest-example-new.jpg
Original: http://pirates.teamofx.us/ss/wiki/quest-example-orig.jpg

That newer way is clean, but I dont think its any easier to read/follow, no table headers further down the page, etc. It runs stuff together, doesnt resize well, I prefer the old/original method it maintains better overall structure, and like being as consistent across the board as we can be until we come up with something better that works across the board. Theres got to be a better way.--OFxZeppers 19:21, 4 September 2008 (PDT)

Yeah we probably need to come up with something completely different --Hile 16:35, 5 September 2008 (PDT)

Here's another idea I just thought of, let me know what you think of it : - ). We can make our own TOC (read above), and then, we can have the words for the name of the quest (where the quest would be bellow it, in white font. We use this for the POTCO Current News and a few other pages on DOW. Would this possibly work? --Haveamagicalday (Talk | Contributions) 16:39, 5 September 2008 (PDT)

I liked Hiles proposed format until I had reviewed longer quests, and observed how the coding responds to resizing (this could perhaps be adjusted through further coding). I believe what makes the organization of this information difficult is that we are attempting to display all of it on a single page (ie the quest page, Gunner (Quest), or Doc Grog (Quest)). It occurred to me that in many cases people referencing the Wiki do not want every shred of information immediately. When I myself reference it, I am generally curious about 2 things, the steps I need to do next, and their rewards. Time permitting I am working on creating a new quest tree that would reflect all tiers/steps, and list the steps simply as thier "Title", "What to get/do", and its "Reward". Each tier/task/step would continue to be documented as it is, but not displayed on the main quest page. Access to this information (ie Exact text, Reward, Spoiler/notes, and picture) would be a click away (when clicking on that listed task). This would streamline the main page and may allow us a better organized page. Some are also comfortable with the current format, so we might actually continue to use it as well, and perhaps offer a link from the main index page thusly...

Story Chapter: The Black Pearl
Second List
Gunner (Quest) - (Full View)

Where clicking on "Gunner (Quest)" takes you to the new synopsis/tree, and clicking Full View, takes us to our current display. I spoke with HAMD about this the other day, we think we could make this work. I hope to have something for review soon in the sandbox.--OFxZeppers 11:55, 8 September 2008 (PDT)

Yes, this idea really could work : - )! Also, having both links on the main page (as shown above), I think would work the best, instead of just having the links to the other type on the quest pages. We can still have that, but having it also on the main page will make it a lot quicker for those people who wish to have it that way : - ). --Haveamagicalday (Talk | Contributions) 12:57, 8 September 2008 (PDT)

So, having the BPQ abbreviated and like the person in the crew's name, and have the rest spelled out? --Haveamagicalday (Talk | Contributions) 12:59, 8 September 2008 (PDT)

Referenced by 2 pages pages that link to “Editing POTCO” — its place in the wiki