Jump to content

Scorp

Developers
  • Posts

    1657
  • Joined

  • Last visited

  • Days Won

    82

Posts posted by Scorp

  1. Checked with author. Conclusion:

    - Stack of https://db.pandawow.me/?spell=136904 is already not applied when melee attack from was boss not successful (dodged, parried...);

    - Player can avoid to receive https://db.pandawow.me/?spell=136922 debuff while under the effect of https://db.pandawow.me/?spell=1022. In case https://db.pandawow.me/?spell=136922 was already applied https://db.pandawow.me/?spell=1022 will not remove it

    https://db.pandawow.me/?spell=136922 is not considered as periodic damage, so https://db.pandawow.me/?spell=114039 reduces damage only by 10%. No information currently that suggests this is not correct

     

    For now closing this ticket

  2. On 12/9/2023 at 3:28 PM, Sqeer said:

    двигаются таймеры по непонятным причинам

    Second boss phase (when he starts using https://www.wowhead.com/spell=131813/wind-bomb) also reduces the cooldown of his "first phase" ability timers such as https://www.wowhead.com/spell=122407/rain-of-blades & https://www.wowhead.com/spell=121896/whirling-blade

    • Yes 1
  3. 7 hours ago, Экзодайк said:

    5:43 и 6:36 за неимением кого либо в рдд зоне скрипт заставил ударить через мили зону, все были под боссом. это не значит что на этом сервере скрипт должен всегда заставлять босса бить этот спелл в активного танка, если ты это делал, то знай что тут баг.

    ps 6:26 один игрок специально вышел в рдд зону чтобы запустить туда от босса этот спелл.

    Your description of expected result is clearly false here. There is no such thing as random target selection for this spell, if there would be - you would see boss turning at a random player every time the spell is casted... good luck stealing the stun buff when you have zero clue which way is he gonna turn. Look at the videos @Silent added above and tell me why boss did not turn to a random player there a single time? Clearly because the logic why would boss turn is something other than "select random player". Normally these kind of cases require further study, at the current state this report is fake.

    • Heart 1
  4. 6 hours ago, Экзодайк said:

    Цель способности Lightning Fists должна выбираться в случайном порядке, в рандомного игрока, но никак ни только в активного танка.

     

    Let's look at your own video - timestamps: 5:43 & 6:36. To which player exactly is boss turning to here? Nobody is even standing there. Review your report 🙂

    • Yes 1
  5. - https://www.wowhead.com/item=71086/dragonwrath-tarecgosas-rest is a CATACLYSM legendary. The effect was disabled on purpose on this server if you use it on a character that is above level 85 approximately 2 years ago. Same goes for similar items / effects

    - https://www.wowhead.com/item=94532/rune-of-re-origination is a PANDARIA trinket. So if it does not work currently as it used to work in 5.4 retail -> open a ticket

  6. я заметил что у босса есть рендж фиксейта и он фиксейтиться на самого дальнего игрока в рамках этой ренджи.

    Но если отойти от босса слишком далеко (больше 100 метров примерно) он тебя не видит и не кидает фиксейт.

    Fatboss guide has excellent explanation how it was working -

  7. Например. Если какой-то босс не поддаётся какому либо ростеру - чтоб она могла его скипнуть. Всё равно этот рейд не увидит Гарроша ТК если какой-либо босс был убит в нормале - Гаррош стоять не будет

    The amount of problems this mop system had that were never solved or properly analysed what is the expected result in each case.... I doubt you want it back

    • Like 2
  8. Ещё стаки не должны вешаться на танков.

    That spell most likely has minimal amount of players it has to hit on each difficulty with tanks being last in priority to avoid the fiasco Garrosh encounter had where mind control was never placed on tank and allowed the boss to be soloed or done with x tanks, completely ignoring the mechanic

    • Like 1
  9. The way it should work is fairly simple:

     

    Encounter Ends / Starts -> Everyone on Conveyor Belt should be teleported down to Main Platform.

    The behaviour between Main Platform and Conveyor belt should be something similar to smoke bomb effect (so if rogue tries to use shadowstep from Main Platform to Conveyor / Vice Versa, then he should receive error message: "your Vision of the target is obscured");

    Once a wave of weapons reaches the end of belt - Blackfuse should pull all players standing on it back to main platform. There should be total of 12 waves of weapons, with 13th being special berserk weapons to wipe the raid.

     

    About Demonic Circles:

    uq0qznE.png

    • Like 1
  10. If the bosses on x 100 are currently working at 90%' date=' then on x5 they are not even working at 50%.[/quote']

    Just to open your eyes, the version currently on x100 realm (which was implemented back in 2016/2017 I believe) is not even close to 60-70% if you go into encounter details (I don't count boss as fully working only because he just casts all his spells displayed in dungeon journal and drops loot). I know what I'm talking about, I have seen the encounters / ways the mechanics are implemented as a developer and as a player. We (development team) ignored this raid almost completely when we started to work towards new x5 with plan to return to it after we finish the other ones in proper order (reason why Siege of Orgrimmar reports are where they are now).

     

    What do I expect from a developer like Dead Mouse? At least an elementary check of their corrections' date=' and not just a correction and publication. If he still tested all 4 bosses before adding them, then he is not suitable for this role.[/quote']

    Now if we return to testing, surely you understand that it is never possible to see all the issues pre-release.

    With patch 5.0 raids it looked like this: they were tested by 2 people me and pelia. We had a lot of knowledge how everything should work / what and how should be tested. + We had help from community guilds who were up to run these raids on PTR and give us feedback. Even with all this there were issues that went live (Nullification Barrier on Feng removed all friendly buffs, legs on Garalon had broken hitbox, aggro bugs on Sha of Fear and so on). Sometimes it was a mistake in code, test/debug code which was left there, late core system update which affected some of raid mechanics that previously worked, bug which could only be noticed with x amount of players, something that did not come in our heads to test as the game offers so many variations for everything and so on. I doubt the development team had this kind of support with this raid, so more things were missed.

     

    My point from all this is - this was raid's first release, bugs are normal - and if you truly want something to be fixed, you need to provide information what exactly is not working. The development plan right now is most likely (I don't know, just guessing) full focus on next raid wings and fix things that are getting reported (right now I see only 3 fresh reports - so only 3 bugs? Sounds that it's not so bad as players say (this is what developers see, because they don't play)). Things like "boss is broken" will get completely ignored by every developer out there, and that's fine, as it gives zero material to work with, just waste of time.

     

    And with reports being ignored - right now there are 3 fresh reports on forums (Siege of Orgrimmar ones). Give the team time and see if they care about them or not to make your final conclusion whenever there is any purpose to report something or not, I can't speak in their place / about their actions.

×
×
  • Create New...