Talk:Builds
From HGWiki
How to edit builds
This is a little help in order to modify or create a new build description in this page.
For each class or quasiclass, you will find a corresponding section. Choose the section accordingly to the build you want to edit or add. When you click on the Edit link next to the title, you will be redirected to an editor filled with content similar to this :
==Blackguard==
{{BuildTable |BuildType=Blackguard| BuildList=
{{BuildDesc |board=openbuild |index=13999|build=Oxec Tuzzom ia Wount| author=strykerofchaos
|BKG=29 |FTR=8 |ROG=3 |[[Drey]] | type=open}}
}}
The first line ==Class Name== is the title of this section.
the following lines are using wiki templates. Notation for wiki templates is {{TemplateName|Argument1=Value1|Argument2=Value2|...}}. the first template "BuildTable" is handling the formatting of the table. The second template "BuildDesc" is handling the output of a row inside the table. Each Build posted here must have his own BuildDesc template. The BuildDesc templates are embedded inside the BuildTable, meaning you should always have a trailing "}}" after the last BuildDesc.
The "BuildDesc" takes several arguments which will be used to display your build inside this page. Each argument is separated with the "|" character.
- board : The first argument is one of builds or buildarchive which indicated which section of the Higher Ground forum to use.
- index : The second argument is the index of your in the Higher Ground forum. This information is displayed when you open your build in a web browser :
You will find a number at the end of the url, after thread= (in this example : 1169554459). This number should be placed inside the index argument. - build : The third argument corresponds to the name of the build. Per convention, please use the same name this build have been posted under in the forums.
- author : The fourth argument is the name of the author. Per convention, please use the name of the user in the forums.
- build breakdown : Next you have to fill up to three arguments corresponding to your build breakdown. For each class used, give the class code followed by the number of level taken in this class. (Example BKG=29, if the build have 29 levels blackguard).
The codes for each class are :- ANY : use this codes to indicate than one or more level are free choices
- AAR : Arcane Archer
- ASS : Assassin
- BBR : Barbarian
- BRD : Bard
- BKG : BlackGuard
- COT : Champion of Torm
- CLC : Cleric
- DRD : Druid
- DWD : Dwarven Defender
- HSC : Harper Scout
- FTR : Fighter
- MNK : Monk
- PAL : Paladin
- PDK : Purple Dragon Knight
- PMS : Pale Master
- RDD : Red Dragon Disciple
- RNG : Ranger
- SHD : Shadowdancer
- SHI : Shifter
- SOR : Sorcerer
- WMA : Weapon Master
- WIZ : Wizard
- recommended races : This argument is the recommended races for this build. Their names should respect the names in this Wiki in order to have the links working. If the race name appears in red after you save the page, it means the name you entered is incorrect.
Unlike the other arguments, the races are not named arguments (ArgName=argument). For example : Elf - [[Aquatic Elf]]|[[Wraith]]|[[Erinyes]]| - type : This last argument is optional, and colors the build's entry in the wiki to represent the special nature or status of the build. If none of the options are applicable, simply leave the "type=" argument out of the "BuildDesc" template. The options are:
- open : Light green, representing that it is an open subrace build.
- recommended : Light blue, representing that the build is known to be very effective and can conquer some of the hardest areas on the server
- archived : Dark gray, representing that build is outdated, although there still might be some relevant discussion.
Discussion
- I believe if this is to be comprehensive then it will get too unwieldy. Therefore we should trim some of the obsolete and poor builds. This is obviously subjective. It is not unreasonable to keep a build listed if it is either important historically or has excellent discussion in the thread even if the build itself isn't up to date.
- We should have some method to highlight exemplary builds. This can be done via a separate page (e.g. HG Epic Builds), or a method of indicating in the table. I propose we add a small box to the left, which can be filled with 1-3 colors indicating whether a build had various properties. These could include highly recommended, proven to demigod, obsolete, and so on. For example:
| Name | Author | Class/Level Breakdown | Recommended Sub-Races | |||
|---|---|---|---|---|---|---|
| Giant of Torm | tyranlthixis | Barbarian: 30 Champion of Torm: 8 Rogue: 2 | Battlerager , Maelephant , Stinger | |||
| Mighty Barbarian | scarfinger68 | Barbarian: 32 Rogue: 3 Weapon Master: 5 | Humanoid - Gnoll | |||
| Obsolete Barbarian | example | Barbarian: 18 Pale Master: 12 Red Dragon Disciple: 10 | Yukio | |||
and implemented with arguments to BuildDesc with things like "recommended=1" and the like. BuildDesc could use IfDef to decide how to highlight. Alternately a single color could be used, with Blue = Recommended and Proven, Green = Recommended, Fuchsia = Obsolete.
Yomi 14:20, 11 January 2008 (CST)
- It's difficult to decide when a build is obsolete. Is it obsolete when it won't get you to a certain area anymore, or is it obsolete when it simply cannot be created anymore? I agree that colour-highlighting the table is a great way to indicate something about the builds, though. BooBooSpooki 07:21, 13 January 2008 (CST)
- So shall we go: red for "defunct due to whatever reason", yellow for "not recommended", green for "recommended/approved by whoever" and blue for "proven demi"? BooBooSpooki 11:36, 17 January 2008 (CST)
- Maybe we need some archived build page that includes the date of the builders last post on it's forum thread. For instance one could say any build that doesn't include paragon level is outdated. --Desocupado 19:32, 1 February 2016 (UTC)
