User talk:Yoshida Keiji/AI behavior update

2nd parameter

I'm thinking we should have a second parameter, which would not display on the skill page itself, but we would type a brief description of the issue into the problem, and then after some dpl template magic via copypaste from other dpl, it would appear beside the skill name on the dpl page. --File:User Chieftain Alex Chieftain Signature.jpg Chieftain Alex 09:46, 23 May 2012 (UTC)

Agree. Second parameters are good to define issues. Propositions as already described for the template:

• No notes.
• No ducuments.
• Poor comments.

...or simply the last words. What ideas do you have?

• Maybe a fourth value could be "inconsistance" between skill page and hero behavior information. Yoshida Keiji talk 10:10, 23 May 2012 (UTC)

e.g. I would put this on the Signet of Creation page: {{User:Yoshida Keiji/AI behavior update|ritualist|*Hero uses within spirit instead of earshot range.}}

And it would appear on the dpl as:

Ritualist skills
Skill name	Description of Issue
Signet of Creation	Hero uses within spirit instead of earshot range.

It was just an idea. File:User Chieftain Alex Chieftain Signature.jpg Chieftain Alex 10:24, 23 May 2012 (UTC)

I like your idea. Second parameter for description and maybe a third parameter to classify "state". With the "description of issue", we face a difficulty though. Because for long time ago even before I came shouting about GoLE, we have different information in two different places: individual skill pages and the hero behavior...so which one will have priority? We make two columns for each? I mean, the transclution onto this list will be ackward. If the community reaches a concesus here Talk:Hero_behavior/Unexpected_behavior#Documentation_Fail, then the individual skill pages description would be the choice. Yoshida Keiji talk 10:37, 23 May 2012 (UTC)

( Idk this isn't my project :p ) I guess the parameters of interest are:

• What the problem skill is (skill name)
• Who isn't using it properly (read: heroes, specific enemy in NM or specific enemy in HM)
• What the problem is. (description)

Perhaps we shouldn't be tagging skill pages at all with this template until we're figured out what we're using it for. File:User Chieftain Alex Chieftain Signature.jpg Chieftain Alex 10:53, 23 May 2012 (UTC)

I have made my mind:

Since we will be tagging skill pages. The first parameter profession, will transfer to DPL with name.

I haven't read any reports about enemy usage so far (if you now, point them). But if it has a named NPC report, we will know so I don't care to be specificly defined within the template.

The description will be a false step for the Project, so better is to return one step back. At the moment we have 6 sources: Skill main page, Skill talk page, Hero_behavior/Unexpected_behavior main page, Talk:Hero_behavior/Unexpected_behavior talk page, specific NPC main page and specific NPC talk page. Using this template to tag should be simplier.

So to the Project what really matters are:

• Empty (or blank, clear, clean, void, none): This will be the same as "Image needed, Project" which will mean clean start for this Project contributor/s.

• Undocumented: This will be the same as "Image update needed, Project". The main differences with images of armor, maps and weapons versus skill notes is that the pictures are not wrong but poor quality or not complying with formatting guideline. But when focusing on skill notes, "undocumented" for the Project will mean to:
  • Remove notes in main pages because they are not verified (which will lower wiki quality standard), but transfer those inputs to its talk page AND this Project space. Plus all comments in talk pages that are unconclusive should be copied (not removed) THEN... bring them here all together and make a collage of reports.

• Verify: Will mean skills have documented research but doubtfull. After all not everything has to be wrong here and some contributions might be accurate. To the Project will mean direct "Testing phase" to confirm.

Yoshida Keiji talk 15:59, 23 May 2012 (UTC)

Just hold back on tagging anything with it - I'm short on time but it is possible to just put {{User:Yoshida Keiji/AI behavior update}} on the page, and the DPL can check the page to see if it uses the skill infobox, followed by it deducing the profession. (you could probably code it given the examples of dpl on the image needed page - it needs to check for the usage of this template, followed by checking for usage of skill infobox, followed by pasting the parameters into the list...) File:User Chieftain Alex Chieftain Signature.jpg Chieftain Alex 16:42, 23 May 2012 (UTC)

L000L I ubber fail... User:Yoshida Keiji/Laboratory. Don't worry, I can wait. Tagging without confirmed parameters is a bad idea anyways. I'm confused I don't understand why you want the infobox data. With {{image update|reason|map}}... "reason" was useful to tell the community what was failing...(UI, References, Slaughtered) If {{User:Yoshida Keiji/AI behavior update|profession|reason}} doesn't have a "reason" parameter... others won't be able to know what is failing for this Project. Yoshida Keiji talk 18:51, 23 May 2012 (UTC)

Deprecated

Considering the currently very limited amount of wiki contributors, in combination with the state of the game, I feel this template is effectively no longer needed. The framework around it has no mainspace use either. Shall we move onto deletion? - Infinite - talk 13:46, 24 December 2017 (UTC)

I have no personal objections, nor can I currently see this template ever being used as intended. G R E E N E R 22:52, 24 December 2017 (UTC)