We are currently in the process of bringing this to 100% working functionality. Any help would be greatly appreciated. Find out more in the Community Portal.

Path of Exile Wiki talk:Community portal/Archive 4

From Path of Exile Wiki
Jump to navigation Jump to search


Archives

Gem quality section

On most skill and support gem pages, there is a section header that reads "Gem Quality" and beneath it is a brief description of what bonuses quality adds to the gem. Given that Template:Gem Infobox displays a field for this, is there any reason to also have the page section that gives the exact same information? Not only is it redundant, but people often update one and not the other which leads to a discrepancy in the information presented on the same page. Can we just get rid of the page section and leave in the infobox section? —Vini (t|c) 23:04, 26 October 2013 (UTC)

New zone templating

I would like to implement new templating for zone info. You can see an example here: Template:Zone/testcases. Comments? Suggestions? —Vini (t|c) 12:36, 13 November 2013 (UTC)

Wow, looks very smooth. I like it. Maybe adding the adjacent areas could be useful information aswell? Like on the version history page, a link to the previous area(s) and to the next. Climmels (talk) 12:51, 13 November 2013 (UTC)
Not all areas have a clear prev and next - would a list of connected areas work? I'm thinking along the lines of wikipedia band infoboxes with lists of associated acts. I don't think anywhere is connected to more than 4 areas (gardens, marketplace, crossroads are all 4s). --Qetuth-(talk) 13:07, 13 November 2013 (UTC)
Might I suggest incorporating the zone banners? Here is the Ship Graveyard banner. Alos, I'm not sure which would be preferable but here is the other waypoint icon, amongst the other minimap icons, that can be used. - FaceLicker (talk) 13:17, 13 November 2013 (UTC)
Looks great, definitely an improvement over the current zone template. I do like the banner Facelicker has linked, though it may be a little too wide at it's current size. Iamacyborg (talk) 13:33, 13 November 2013 (UTC)

Korean Language Pages

Hey, I've been contacted by Noala Entertainment who want to start translating wiki pages into Korean, don't be surprised if you start seeing these pages start to crop up on the wiki. Iamacyborg (talk) 12:08, 14 November 2013 (UTC)

Map boss videos

Magier556 has previously been putting links to his map boss videos on the corresponding map pages. As was discussed, we reached a consensus that this was okay to do since it provides supplementary content to the wiki, even if the videos are being monetized. Given the choice between linking to monetized videos that have useful commentary and not linking to anything, I am in favor of the first option. However, if other people want to link to videos that are not monetized and provide commentary that is as useful or more useful, I think we should showcase those instead. —Vini (t|c) 21:42, 17 November 2013 (UTC)

I agree with both your points. I also still think we need basic video demonstration of all the skills as they're more useful than static screenshots or gifs. Iamacyborg (talk) 23:01, 17 November 2013 (UTC)


Videos

I've just added a video by ZiggyD to the Flask page. What does everyone think? Is this something we want to be doing, is it useful to the community? Iamacyborg (talk) 20:29, 20 November 2013 (UTC)

I think this is something we should include videos that are useful and relevant to the page, but not if they simply repeat the content of the wiki page. The flask one is a good example in that he talks about the reasons and tactics behind flasks, while the page contains factual information about them.CosmicChopsticks (talk) 20:55, 20 November 2013 (UTC)
Yep, I totally agree with you. There's definitely some information which is more easy to show via video, for example map and game boss fights are easier to show via video, whereas some subject are more easily explained via the wiki itself. For example, a video showing what Vendor Recipes are and how they work in PoE would be useful, whereas a video showing off every single vendor recipe would not. Iamacyborg (talk) 21:11, 20 November 2013 (UTC)
That reminds me, I had assumed that the boss videos on the map pages aren't embedded due to it not being possible in Gamepedia, but the flask video shows that this isn't the case. Should those be embedded instead of linked to Youtube? CosmicChopsticks (talk) 21:29, 20 November 2013 (UTC)
It's definitely possible, check the syntax used on the flask page, and here: http://www.mediawiki.org/wiki/Extension:EmbedVideo I think we need to take a look at the videos before embedding them, I know the video creator has been adding those there himself and we need to check they're of sufficiently high quality to embed. Iamacyborg (talk) 21:40, 20 November 2013 (UTC)
I'm fine with embedding the flask guide video on the Flask page. It's a well-made video and contains tips that aren't included directly on the page. Can we limit the width of embedded videos to 300px though? Any larger and it starts encroaching far into the content area on smaller resolutions. —Vini (t|c) 22:03, 20 November 2013 (UTC)
Yep, I'm happy for them to be that size. Iamacyborg (talk) 22:36, 20 November 2013 (UTC)

Skill screenshots

As a new project I'm making sure all of the skills have good screenshots. Right now the following have none: Storm Call, Enduring Cry, Devouring Totem, Glacial Hammer, Ground Slam, Smoke Mine, Animate Weapon. Also I think some could use improvement: Bear Trap (higher resolution to see used trap), Elemental Hit (better view of attack+ele effect), Puncture (show attack, show moving monster with blood trail?), Viper Strike (show poison charges, clearer attack), Arc (clearly show chaining), Conductivity (zoom out), Firestorm (zoom out), Ice Spear (maybe show both forms), Raise Spectre (better quality, zoom out)

We could also do screenshots for support gems: Ranged Attack Totem, Spell Totem, Chain, Culling Strike, Fork, GMP, LMP, Pierce, Multiple Traps. Or whatever. If anybody wants to help I'd appreciate it. Magnanimous2 (talk) 10:30, 29 November 2013 (UTC)

Over time I've been working on uploading skill screenshots. Believe it or not, it's requires a lot of effort to get nice looking screenshots. I did my best with Bear Trap, but it's still somewhat difficult to see since the skill's actual graphics don't stand out a lot. You also said that it should be higher resolution; well I'm running 1920x1080. Do you have some crazy high resolution? In any case, I'd certainly appreciate the help in getting a nice looking screenshot for each skill. —Vini (t|c) 11:09, 29 November 2013 (UTC)
Resolution was the wrong word, yeah. Bear trap was definitely the hardest to get a good shot of so far, but I eventually got two good ones. The trick was finding enemies that don't touch the ground: Media:Bear_Trap_skill_screenshot_2.jpg (and getting lucky with timing but the quality was a little off). Also I tried to upload a new version of the existing file, but it isn't working for some reason. Magnanimous2 (talk) 07:33, 30 November 2013 (UTC)
I'll have a new computer within a week, so I'll finally be able to get high quality screenshots. I'll also make some efforts to try some basic skill videos to see if they'd be more suitable, for example a video showing off Bear Trap would probably be clearer than a screenshot. Iamacyborg (talk) 14:57, 30 November 2013 (UTC)

Update: I just added Barrage, but now we need Flameblast (I don't have the gem and can't be arsed to get one >_>). Currently missing are Enduring Cry, Devouring Totem, Animate Weapon, Ranged Attack Totem, Spell Totem, Multiple Traps. Magnanimous2 (talk) 18:14, 23 December 2013 (UTC)

TODO Tag/Page or Similar Expansion to Stubs

Has there been any thought or talk about adding a TODO page or Addition to Stubs.

Stubs are good at what they are for, to indicate missing information. What they are not good for is telling what information is missing from a page and they are not good for the concept of an easy to read list of TODO's with links to the page in addition to what the page is missing for incomplete pages/tables, for new pages, or new features that need volunteers to get it done. Example: A lot of gem pages are missing general information or additional info and there is no tag or page to show that they are missing that information besides the possibility of adding the stub tag which doesn't tell what is missing.

I understand that the community portal has a Project section, which is good for general TODO's on a bigger level. But I feel there should be a link under Projects that links to a TODO page. The TODO page would be where as someone finds something missing from a page but doesn't have the ability, time, knowledge, items, or etc to test and then add the missing data could just add it to the TODO Page under a fitting category.

How I imagine the best way to implement it based on a scenario of its usage:

Scenario (It got long and is still missing some ideas or descriptions.)
Your browsing the wiki and you come across a gem page missing the information for level 15. Your crunched for time and don't have time to log in and check and/or you don't have the gem and would take a while to level the gem up.

At this point there are two things that could happen.

1. The complicated way that I have no idea if it's even possible. You go into edit on the gem page and add a tag at the bottom or top with some call that would indicate the base tag = TODO, the subsection tag = Gem, the TODO info text = Gem Level 15 missing all relevant Data. Something (a Parser, template, or something) would be able to take that information and dump it into a TODO Page under the subsection tag with a link to the page and a discription of what the TODO is. The TODO line added would probably look like:

  • Storm Call - Gem Level 15 missing all relevant data.

The Subsection Tag would likely only have 5 possibilities: Gems, Items, Quests, Mechanics. Though it could be that it is just an addition to the TODO description. I'm also not certain how it would look or have to look do to how it'd have to be implemented

2. You see something is missing. Quickly you go to the left of the wiki page click Community Portal page and click a link under the Projects section to the TODO page. You scroll to the gem section and then click edit and add a entry similar to:

  • Storm Call - Gem Level 15 missing all relevant data.

The second one is much easier to implement and is actually possible to my knowledge. Possible sections of the TODO page are Gems, Items, Quests, Mechanics. Each patch could also have its own section added with entries similar to:

  • Mechanics: Ignite - The Ignite status ailment now deals only 20% of the original hit per second for 4 seconds. This has been reduced as it can be increased in more ways with the damage over time changes.

If this exists or is a bad idea I'd like if someone told me so. As if it does a link needs to exist on the main page and on the community portal page. I ask this because it is hard to find things that need to be done that you would have the means to do outside of the maintenance category page. It also adds the possibility that for a big update or more complicated one someone could claim it and state that they are working on a particular TODO entry or part of that entry. Ebonmourn (talk) 05:55, 30 November 2013 (UTC)

I think it's a good idea to have specific projects to attract new editors. I would divide it into skills, items, quests, races(especially chest info), game mechanics(and making sure they're correct; sometimes people in global have two or three answers), then lore/general topics. Magnanimous2 (talk) 07:42, 30 November 2013 (UTC)
Sorry if this is explained above and I'm missing it, but IS there currently a way to easily indicate that a particular page should be added to a/the TODO list? For example, the Fire Totem gem page is in need of an update for the changes from 1.0.0 for gem levels 7+. What exactly should be done to show this on the TODO page? 777isHARDCORE (talk) 09:18, 7 December 2013 (UTC)

Microtransaction Pages

I've been thinking for quite some time now that the MTX pages need an overhaul to match the rest of pages on this wiki. These pages are only going to grow in the future and I believe it would be best if we get the formatting done now while it's still manageable. This will be especially important for the Pets, Item Effects (which has recently been renamed to Armour Effects) and Alternate Skill Effects pages. Now, since those pages in particular contain actual in game items, it only seems appropriate that we create individual pages for each mtx utilizing the item template that we use for all other in game items. We could also add in the Path of Exile website descriptions since they differ from the mouseover descriptions in game. We could go back to embedding GGG's video previews on the individual pages since it will now be 1 video per page instead of 30 videos.

MTX items use the currency item format in game and so this should be a relatively simple task to set up item templates for transclusion especially considering that all the info we need is in the game data. To give people an idea of what mtx items look like in game, here are a couple basic examples: Lua error in Module:Item2/core at line 517: attempt to index field '?' (a nil value). Lua error in Module:Item2/core at line 517: attempt to index field '?' (a nil value). The only thing missing is a line that appears above the stack size on some items that indicates whether the item is a Rain of Arrows Skin, a Helmet Skin, a Helmet Attachment, a Weapon Effect or one of the many other mtx types. A quick edit to the item template should be able to fix that. I'd like to ask help from more experienced wiki editors in making this transition especially with the template and translcusion. As I said, all of the pertinent info that we need such as stack sizes, mtx type, effect descriptions and help texts is contained in the game data (the CurrencyItems.dat file to be specific.)

I can make the required changes to the template. —Vini (t|c) 02:05, 24 December 2013 (UTC)
All set. Here is an example of the correct templating:
{{Item | View={{{View|}}} | Format={{{Format|}}}
| Name                   = Skull Hood
| Type                   = Microtrans
| Subtype                = Helmet Skin
| StackSize              = 20
| Effect                 = Adds the appearance of a hooded skull to your headdress
| HelpText               = Right click this item then left click a head slot item to apply it.
}}
Thanks Vini. With Steam marketable microtransactions we might also be able to embed price history and things like that as well which should be useful to the community. Iamacyborg (talk) 13:09, 24 December 2013 (UTC)
I created a stub page for the Radiant Weapon EffectRadiant Weapon EffectWeapon EffectAdds a radiant effect to any equipped weapon that includes the necessary templating. Currently, the auto category doesn't work for the "Microtrans" type, but I will fix that. —Vini (t|c) 23:09, 24 December 2013 (UTC)

Drop rates for items / Spawn rates for affixes

I'd like to add this kind of information on the wiki but I'm not sure how to present it. The numbers are different for each item class (those are only valid for 2-handed axes) and obviously they're also different for lower ilvls (you can't get all affixes if you ilvl is lower than 77). Any suggestion? Or maybe you just think it's useless? Chriskang (talk) 13:42, 6 January 2014 (UTC)

I think it's definitely useful to have this information here somewhere, though the best use would be a dedicated calc site that lets people work out crafting percentages per item per level. Is the percentage chance different for every single ilvl? As far as presenting it, maybe a dedicated crafting page per item that lists possible affixes, required ilvl's and chance rate? Iamacyborg (talk) 14:23, 6 January 2014 (UTC)
The game file actually contains a "weight" for each affix and this weight can be different from an item to another. For example, the "Heated" prefix has a very high weight on axes (1200) but is quite low on maces (500).
This number is then divided by the sum of all affix weight available for this ilvl and for this item.
Let's take a simplified exemple. If the drop pool contained only the following affixes for axes:
Item Affix Affix level Weight
Remora's 9 1000
Lamprey's 25 500
Vampire's 72 250
You would get:
  • Chance to get "Remora's" on an ilvl 75 axe = 1000/1750 = 57% (1000 = Remora's weight; 1750 sum of all weights)
  • Chance to get "Remora's" on an ilvl 50 axe = 1000/1500 = 66% (because "Vampire's" is not available at ilvl 50)
  • Chance to get "Remora's" on an ilvl 20 axe = 1000/1000 = 100%
As you can see, every new affix in the pool changes the pool size at its ilvl. If you add an affix "Foo" with an affix level of 50 in the table above, it changes the pool size between ilvl 49 and ilvl 51. So, to answer your question: yes, the numbers change slightly at every single ilvl. Chriskang (talk) 16:15, 6 January 2014 (UTC)