User talk:OmegaK2

From Path of Exile Wiki
Jump to navigation Jump to search

Known problems, but won't be fixed any time soon or can't be fixed:

PyPoE and changes to aura modifiers

Hello, hopefully it's the right place to provide such feedback. I have a problem editing the watcher's eye page and modifiers associated with auras. I was going to edit some of them, but noticed the red text above and that the bot makes all changes. Well... Including some funky stuff, like changing cold multi and chaos multi modifiers to just "damage over time multi". Now, the problem is that in patch 3.8 there were a few changes made to watcher's eye and some of those modifiers are still available in standard league, but cannot be generated anymore. This creates three problems:

  1. Some "legacy" modifiers are still showing there, without any reminder that they can no longer be obtained.
  2. Malevolence has no legacy modifiers listed, instead one new modifier is repeated three times. Technically those two old modifiers don't exist anymore and were merged into the new one.
  3. I have no clue how to edit those Modifier:Aura pages without later being incorrectly overwritten by the bot. Also, I made one test-edit and it didn't do anything (sorry, I'm bad at programming so I simply don't understand what's going on).

For reference, a quote from patch 3.8: "Watcher's Eye: Can no longer gain +% to Cold and Chaos Damage over Time Multipliers while affected by Malevolence. Instead now has +% to Damage over Time Multiplier while affected by Malevolence. This affected all versions of the item. The mana cost reduction while affected by Clarity now specifically applies to non-channeled skills. The mana leech while affected by Wrath is now Energy Shield leech while affected by Wrath."

  • Shalq 16:06, 5 March 2020 (UTC)
I took the liberty to format your post a little because it was hard to read.
Legacy modifiers should be removed from the item itself and not the mod pages. Mod pages are only removed if the actual mod with the ID no longer exists, which hasn't been the case so far.
From queries (like watcher's eye) you can remove modifiers by adding AND NOT IN ("IdOfTheModThatShouldNotBeThere", "IdOfTheModThatShouldNotBeThere2"), if it is just a list of modifiers, remove the incorrect ones. You can exclude the duplicates with the same process as well.
There isn't really anything funky about those bot changes in particular though, it just reflects what GGG has done, they just replaced the old 3 versions with the new stat. --OmegaK2 (t|c) 17:32, 6 March 2020 (UTC)
Thanks for an explanation and sorry for the lack of formatting. I've made some edits to the Watcher's Eye page.
Does the existence of a page like this one mean that the bot pulls all information straight from the game files? So even if there are some unused (as in, not actually implemented) things like the aforementioned WE mod, they're still going to be automatically put up on the relevant pages?
Shalq 20:59, 6 March 2020 (UTC)~
Yes, all the pages in the special name spaces are generally pulled directly from the game data (modifiers, areas, passives, monsters, etc). Some pages, like base items and prophecies can also be updated via bot. There is still a bit of formatting done on the data to make it more usable on the wiki before hand though.
Whether these are automatically put anywhere depends on the query used. For some unique items like watcher's eye we don't actually know how it exactly it selects the mods, so a more broad query was made which needs some manual exclusions. For some other things, like which mods can appear on randomized items we know how it works for the most part so we can replicate what the game does with the data provided. --OmegaK2 (t|c) 16:09, 7 March 2020 (UTC)
Thank you for a comprehensive explanation! I'm going to keep that in mind whenever GGG makes similar changes.
Shalq 00:50, 9 March 2020 (UTC)

old stuff

hey grandpa! you do not see on еру first level he has Done 7-11?—Preceding unsigned comment added by Hulgun (talkcontribs)

Hey, OmegaK2. I'm referring to exalted orb drop level restrictions revert-change: Unfortunatelly there is no video evidence, but on other hand the exalted was found in normal ledge by myself. That's why I modified the page. Additionally, I searched reddit for more evidences and added the link. I did't find and newer topics, so linked that one. That's not a big deal, we can keep the 35th level of acquisition, if you think my source is compromised.—Preceding unsigned comment added by Voiza (talkcontribs)

See Talk:Exalted Orb for a general explanation. When did you find exalted orb (which league) and under what conditions? (any active prophices? etc) --OmegaK2 (t|c) 16:38, 25 April 2017 (UTC)

Skill progression

Hi, here I am trying to transfer your templates to the py version of the site, and started with such problems... By inserting the template "Skill progression", the page does not load in general, similarly with other subjects, while only skill stones work, as an example: ru:Тест песочница GAPON. Do not tell me what could be the trouble? And yes, such another question, when renaming stone tags, shows the module error, how can this be fixed?
Thank you in advance. Kordloperdlo (talk)

By the looks of it, the cargo values for the skill progression (skill_levels and skill_stats_per_level) are not set correctly, so skill progression can't query them --OmegaK2 (t|c) 09:03, 23 March 2018 (UTC)
Ok, but could not tell where to look for at least these (skill_levels and skill_stats_per_level), since I copied from you the same?--Kordloperdlo (talk) 09:44, 23 March 2018 (UTC)
You didn't create the cargo tables. Template:Skill/cargo/skill_levels and Template:Skill/cargo/skill_stats_per_level has the declaration calls on this wiki --OmegaK2 (t|c) 16:33, 23 March 2018 (UTC)
Created, installed, but when the template is inserted (Skill progression), the page also does not load. Maybe there are not enough properties, parameters, mods?--Kordloperdlo (talk) 17:26, 23 March 2018 (UTC)
I checked and it seems you didn't create skill_levels. By the way it might also be possible that some missing tables might also cause problems. I'd recommend going through Special:CargoTables here and make sure to each and every one of the cargo tables defined from version, skill, mods, items are defined if you intend to copy over the modules to the russian wiki. if you look at the code, the modules depend on various other cargo tables existing so I can't say for sure what breaks exactly.--OmegaK2 (t|c) 22:03, 25 March 2018 (UTC)
Hey. tell me please how you created the Cargo table - "_pageData", "versions", "weapons", "item_buffs", "monster_resistances". Thank you.

List of troublesome data

Creating a list of modifiers, skills or passive skills that are repeatedly changed and does not appear to have any other fitting modifier. Feel free to add or remove rows. --Illviljan (talk) 06:32, 8 April 2018 (UTC)

Bot not exporting Advanced Traps Support

Hey Omega, not sure the best way to contact you about this, but I moved Trap Cooldown Support to Advanced Traps Support since the bot didn't do it initially. Can you have it export the new skill data? I updated the cooldown progression, but I didn't want to update the others manually if I could help it.—Preceding unsigned comment added by Yamin66 (talkcontribs)

PyPoe (Russian)

Will PyPoe be able to work on the Russian wiki?--Ruba159753 (talk) 09:05, 5 September 2018 (UTC)

I'll have to add support for that specifically. A significant portion of some of the exports for items takes care of managing name-conflicts in the name space though which I probably can't help much with though since I don't speak russian or frequent that wiki. In addition, the export is intended to be used with the templates/modules accordingly, you'll have to port/copy those over as well, but that should be easier since I've taken some steps to make adjusting the language easier. --OmegaK2 (t|c) 04:13, 7 September 2018 (UTC)
Well, you can redirect the bot to the Russian wiki, with the English names of mods, locations, because more than 40 thousand pages are hand-made, like a lot ... Thank you.--Kordloperdlo (talk) 09:41, 17 September 2018 (UTC)
I've updated PyPoE just now to add support for other languages and as well as the russian wiki. It is by no means complete at the moment, a lot of the specific handling for name space conflicts and inter wiki linking so on are missing at the moment, but I think it may be good enough. If you send me specifics I can probably also adjust it so it works for your wiki
To use the other language use pypoe_exporter config set language Russian.
You can generally see what the output would be if you do --write instead of --wiki directly, but writing to the wiki I haven't tested yet.
--OmegaK2 (t|c) 12:58, 6 October 2018 (UTC)
Thank you! We will try and test.
And what specifics are you talking about? What exactly do you need to provide?
Like began to understand, but the editing of pages takes place on the English wiki, not in Russian.
--Ruba159753 (talk) 14:01, 6 October 2018 (UTC)
In "Divination Card" description {{c|normal| has changed to {{c|white|, because of this color does not work.
When create a page "Divination Card" with the name that is already there, it is added (divination card) - please change to (гадальная карта).
When create a page "Prophecy" with the name that is already there, it is added (prophecy) - please change to (пророчество).
Trying to create "Active Skill Gem" or "Support Skill Gem" pages with a name that already exists, the page is not created or edited, but skipped. Example: Portal (gem).
Possible name conflict: - "Сапоги ученика" is a Scholar Boots.
Avian Twins Talisman is a "Талисман пернатых близнецов", please change the text in brackets:
  • (Fire Damage taken as Cold Damage) → (получаемый урон от огня становится уроном от холода)
  • (Fire Damage taken as Lightning Damage) → (получаемый урон от огня становится уроном от молнии)
  • (Cold Damage taken as Fire Damage) → (получаемый урон от холода становится уроном от огня)
  • (Cold Damage taken as Lightning Damage) → (получаемый урон от холода становится уроном от молнии)
  • (Lightning Damage taken as Cold Damage) → (получаемый урон от молнии становится уроном от холода)
  • (Lightning Damage taken as Fire Damage) → (получаемый урон от молнии становится уроном от огня)
Monkey Paw Talisman is a "Талисман обезьяньей лапки", please change the text in brackets:
  • (Power Charge on Kill) → (заряд энергии при убийстве)
  • (Frenzy Charge on Kill) → (заряд ярости при убийстве)
  • (Endurance Charge on Kill) → (заряд выносливости при убийстве)
Two-Toned Boots is a "Двухцветные ботинки", please change the text in brackets:
  • (Cold and Lightning Resistance) → (сопротивление холоду и молнии)
  • (Fire and Cold Resistance) → (сопротивление огню и холоду)
  • (Fire and Lightning Resistance) → (сопротивление огню и молнии)
Serrated Arrow Quiver (Descent) is a "Колчан зазубренных стрел (Спуск)", please change the text in brackets.
I repeat here:
  • Error with unique items whose base items have |purchase_cost: attempt to get length of local 'data var' (a nil value).
  • For example:Кровь_каруи
  • I think it's because of the translation of |rarity. Due to the fact that the bot changes rarity to Russian, it was necessary to rename "Normal, Magic, Rare and Unique" in the module "Module:Game". The only thing that did not rename, so it is long_lower =.
  • In principle, to translate "rarity" into Russian is not particularly necessary, because before all was well. So, if the problem is in translation into Russian, it is possible without it.
--Ruba159753 (talk) 11:44, 22 October 2018 (UTC)
resolved [Expand]
The problem with lua: items that need to be unique are defined as magic -
--Ruba159753 (talk) 10:12, 19 October 2018 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── Need this translated for it to work:

        'English': {
            # A2: Though Scared Ground
            423: "Survival Instincts", # Veridian
            424: "Survival Skills", # Crimson
            425: "Survival Secrets", # Cobalt
            # A5: The King's Feast
            454: "Poacher's Aim", # Verdian
            455: "Warlord's Reach ", # Crimson
            456: "Assassin's Haste", # Cobalt
            457: "Conqueror's Efficiency", # crimson
            458: "Conqueror's Potency", # cobalt
            459: "Conqueror's Longevity", #viridian
            # A5: Death to Puirty
            560: "Rapid Expansion",
            780: "Wildfire",
            777: "Overwhelming Odds",

            775: "Collateral Damage",
            779: "Omen on the Winds",
            781: "Fight for Survival",
            784: "Ring of Blades",

            778: "First Snow",
            783: "Frozen Trail",
            786: "Inevitability",
            788: "Spreading Rot",
            789: "Violent Dead",
            790: "Hazardous Research",

--OmegaK2 (t|c) 13:00, 20 October 2018 (UTC)

Names of jewels, types of jewels and quests translated:
        'Russian': {
            # A2: По святой земле
            423: "Инстинкты выживания", # Бирюзовый
            424: "Навыки выживания", # Багровый
            425: "Секреты выживания", # Кобальтовый
            # A5: Пир вождя
            454: "Браконьерство", # Бирюзовый
            455: "Длинные руки ", # Багровый
            456: "Бойкий убийца", # Кобальтовый
            457: "Смекалка победителя", # Багровый
            458: "Могущество победителя", # Кобальтовый
            459: "Живучесть победителя", #Бирюзовый
            # A5: Смерть Чистоте
            560: "Быстрое расширение",
            780: "Степной пожар",
            777: "Подавляющее превосходство",

            775: "Сопутствующий риск",
            779: "Знамение ветров",
            781: "Борьба за жизнь",
            784: "Кольцо клинков",

            778: "Первый снег",
            783: "Мерзлый путь",
            786: "Неизбежность",
            788: "Гангрена",
            789: "Ярость мертвецов",
            790: "Опасная наука",
--Ruba159753 (talk) 14:08, 20 October 2018 (UTC)
A mistake, it turns out in Russian:Проч. Items:, but it is necessary: Проч. Предметы:. (For example: Deafening Essence of Sorrow) (Although in the game itself in the singular indicated "Item/Предмет".)--Kordloperdlo (talk) 11:45, 24 October 2018 (UTC)
Question about microtransactions: is there any reason why microtransactions have different sizes (1 or 2)?
About mods: (Hidden) mods are not translated. Do you need to provide a translation or does it go somewhere in the game data files?--Ruba159753 (talk) 16:27, 25 October 2018 (UTC)
The upgraded_from_set options with Notes in English have already been added to Essence. Is it possible to translate the text into Russian, or to make sure that it does not change, after editing manually when you restart PyPoe?
  • random Essence → случайная Сущность
  • random Shrieking Essence → случайная Визжащая Сущность
  • random Deafening Essence → случайная Оглушающая Сущность
  • type change corruption outcome → изменение типа в результате осквернения
  • +1 level corruption outcome → +1 уровень в результате осквернения
--Ruba159753 (talk) 12:47, 18 November 2018 (UTC)
In Area data, specifically in maps, the main_page parameter produces an incorrect page name. Is it possible to leave this parameter without translation (we have redirects)? Or at all to remove it from export since it spoils everything. As I understand it, it adds the word "Map" to the data from the |name parameter. Unfortunately, we have in the language a little differently =) Or tell us what information you need to provide to make it work properly? For example, id MapWorldsBazaar data: at the moment, like this Базар Map (Война за Атлас) and should be here is how Карта базара (Война за Атлас).
--Ruba159753 (talk) 19:03, 19 November 2018 (UTC)
Harbinger Map is a "Карта Предвестника", please change the text in brackets:
  • (Low Tier) → (низкий уровень)
  • (Mid Tier) → (средний уровень)
  • (High Tier) → (высокий уровень)
--Ruba159753 (talk) 18:59, 24 November 2018 (UTC)
PyPoe removes the main_page parameter that we added manually from the Passive_Skill pages.--Ruba159753 (talk) 16:56, 26 November 2018 (UTC)
Modifiers with similar <if:MS>{Болезненный}<elif:FS>{Болезненная}<elif:NS>{Болезненное}<elif:MP>{Болезненные}<elif:FP>{Болезненные}<elif:NP>{Болезненные} names are not edited PyPoe. When you try to edit it, it looks something like this:
One or more conditions failed on page "Modifier:LocalAddedPhysicalDamageTwoHand2". Skipping. No wiki page candidates found, skipping this row.
Remembering our conversation about them, I still take advantage of your offer to get rid of excess and ask you to leave only the first name of all listed.--Ruba159753 (talk) 19:03, 27 November 2018 (UTC)
Hello! Error while executing the command pypoe_exporter wiki lua bestiary: Screenshot. The problem, apparently, because of this - Screenshot.--Ruba159753 (talk) 09:19, 2 December 2018 (UTC)
Hello! PyPoe removes the screenhot_ext parameter from Area_data pages.--Ruba159753 (talk) 11:49, 4 December 2018 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── The names of NPCs in brackets after "Book of Reform":

  • (Eramir) → (Эрамир)
  • (Alira) → (Алира)
  • (Oak) → (Дуб)
  • (Kraityn) → (Крайтин)

--Ruba159753 (talk) 20:36, 13 April 2019 (UTC)

Hello! If the map has a unique version, the atlas_connections parameter does not translate this unique version into Russian. Is it fixable? Screenshot--Ruba159753 (talk) 18:16, 4 October 2019 (UTC)

"Usage in upgrade paths" duplicates results

The results are taken from each page where the source element is involved. So, on the example of Orb of Fusing we can see that Hybrid Flasks in a double instance (i.e. data from the pages of Life and Mana Flasks are taken, though recipes are the same)--Ruba159753 (talk) 08:22, 25 September 2018 (UTC)

I don't see any duplicates. Those are two separate recipes. --OmegaK2 (t|c) 09:32, 25 September 2018 (UTC)
Sorry for the inconsiderate =) --Ruba159753 (talk) 09:49, 25 September 2018 (UTC)

New map id

I would like to add new upgrade path of map to the wiki, but i am not sure the new item id of those new map, so i use _page parameter for test edit in Atoll Map (Betrayal). Neokowloon (talk) 03:56, 18 December 2018 (UTC)

They're not new items, they kinda inherit all their stuff from the war for the atlas maps and get some new properties slapped on (like tier, item icon, tags for atlas item drops). I didn't use inheritance here on the wiki because I felt it would be rather confusing (and is also a pain to update), so they're just new pages; so in conclusion there isn't really a new id for the maps --OmegaK2 (t|c) 04:05, 18 December 2018 (UTC)

Unique map

Since Unique map are the same in mechanics but would it better to create new page for the new map item, it seem not right when there is no unique variant of Atoll Map (Betrayal). Neokowloon (talk) 03:58, 18 December 2018 (UTC)

I agree, that is the plan anyway. --OmegaK2 (t|c) 04:05, 18 December 2018 (UTC)

Atlas bases

I just got a Fingerless Silk Gloves drop from a random monster inside the Thicket map and it doesn't show up under "Items found in this area". And I can't seem to add it manually like for cards. Just got Two-Toned Boots (Fire and Cold Resistance) inside the Desert map also. —Preceding unsigned comment added by Blue1231231 (talkcontribs)

This is a caching problem with cargo and can be fixed by null-editing. I did it for both pages. --OmegaK2 (t|c) 14:14, 21 June 2019 (UTC)

The Templar Courts area info problem

Hey there, just wanted to let you know that Area:1~5~4 produced some sort of Lua error with vaal_area_ids = 1_Sidearea5_4 -- while I adjusted it so that the Infobox would show up, I have no idea how to fix it permanently and the message at the top of the window said to let you know. Thanks in advance. (edit: there's also an issue with The Torched Courts (Act 5) not pulling up the infobox Area:1~5~4b correctly either, but there's no Lua error shown on the data page.) Techhead7890 (talk) 15:17, 3 May 2020 (UTC)

I later noticed that 1.5.4 and 1.5.4b were missing from Special:CargoTables/areas but as of today, got added. Thanks to you and Neokowloon for fixing that! Techhead7890 (talk) 15:29, 4 May 2020 (UTC)