Trinitycore: Dynamic Difficulty Map

[gyullo]

I test this function and its not working, first i enter normal and try to change to heroic (i met the requeriments) but didnt change, so i go out, and reset the raid, then i enter again in normal mode, kill marrowgar, go out change to heroic (same size) and enter aain and marrowgar was there.

10 and 10H should be only one raid, the same happen to 25 and 25H. So when you kill one boss in Normal you cant do it in heroic after that. Even trash too, when one is dead in 10N then is dead 10H. ICC is just 2 raids, 10 and 25; the difficulty just chenge the bosses or mini bosses, and the loot.

The reset of both mode (n and h) should be at the same time (this is working good)

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[Jildor]

Confirm

[Betaman2k]

u must clear first 10 normal, then u can used 10 H modus, the same 25 first normal cleared then 25 H ( kill all bosses cleared the instance )

[Ric101]

Confirmed, totaly
IDs should be shared, between Normal and Heroic for Raids, you can do EITHER Normal or Heroic

Furthermore, you should even be able to change the mode inside the instance for Raids such as ICC

[Liudvikask1]

Can you please show the source of this info ?

[Ric101]

http://wow-ladies.livejournal.com/14259851.html

But theres even information about this on old "Blue" posts

[gyullo]

Quote:
DifficultyEdit Difficulty sectionEdit

Icecrown Citadel will be home of the updated instance difficulty setting which can be changed on a boss per boss basis. It will be able to be switched at any time during a raid without leaving and reentering the instance.

Some restrictions on when you cannot change it will be in place. Such as, you cannot change the difficulty in combat or during certain scripted events. To enable it you will have first have to have defeated the Lich King on normal mode, and heroic mode will not affect trash in any way and will only change the bosses.[1]

Source:
http://www.wowwiki.com/Icecrown_Citadel_%28instance%29

Or just read the 3.3 patch note

[xpzz]

the question is... all raids that have normal and heroic mode.. share this cooldown, but icc not...

[FlyerDragon]

Any news? Really important now that we have the Lich King!

[Ryukickass]

Also aren't players suppose to be able to get in 10/25 cif the leader has the achievement because that doesn't work either. It would be nice to get it working since players that get killed by val'kyr don't get the achievement and can't go hc.

[devilcoredev]

Confirm, does someone have a fix for this bug?

[ultimatexemnas]

any news?

[Star-lion]

this isnt actually a bug its a nyi feature

[timothy003]

@kandera Heroic difficulties using separate instances is a bug, though.

[Star-lion]

no in icc having heroic/normal in the same instance is a feature that we dont have implemented yet

[timothy003]

Okay.

[ChristophWeigert]

Wasn't the shared ID a feature of Cataclysm and not WOTLK?

http://us.battle.net/wow/en/game/patch-notes/4-0-1

"Icecrown Citadel and Ruby Sanctum now use the new Flexible Raid Lock system"

[Aokromes]

It was also 3.3.5a feature from normal to heroic mode.

[ChristophWeigert]

Ok thx @Aokromes.

I did some research on wowhead (http://old.wowhead.com/zone=4812/icecrown-citadel)

Just one question (Because I never played on retail), if you choose to kill Professor Putricide on normal mode can you do lich king on heroic mode?

[Shauren]

@Giswald no - you must kill them all on heroic to access heroic LK

[dr-j]

why is this priority low when this is a major bug on tc servers (not the bit about being able to change difficulty setting while in ICC, even though would be nice for this to be fixed), the major issue is that player is only meant to have one id to do icc10 in either n/h, one id to do icc25 in either n/h, one id to do rs10 in either n/h and one id to do rs25 in either n/h

At the moment due to player been able to kill all bosses in both normal and heroic modes (ie ids are not shared,

• Players get double the number of eof they are meant to get from killing bosses in these instances if they do 10n/10h/25n/25 h
• Double chance for quest items for sacred and the corrupt each week making sm easier to get
• More primodial saronite from bosses than should be also making the above quest easier
• More chances of obtaining shadowfrost shards per week making sm easier to get than should be
• Twice as many chances to obtain tier tokens from bosses in ICC

[Shauren]

@dr-j theoretically this is not a bug but an unimplemented feature - both being able to change difficulty inside and sharing the lockout between n/h is linked to the same flag in Map.dbc

Also, don't just come here and say "oh but this is major for me/users" - in reality it is very minor compared to other stuff (only 2 maps out of ~300? use this)

[dr-j]

as I said would be nice to be fixed, main reason I commented here was about why tagged as low priority.

[Aokromes]

Test https://github.com/TrinityCore/TrinityCore/pull/12690

[Rushor]

actually this patch works nice for the saved ids

example:
1) go to 25nh
2) kill marrowgar
3) leave instance, change map to 25hc
4) join instance
= > result: you will be in 25 nh again

BUT:
IF you change it from HC to NH it's not working and you get a second ID

example:
1) go to 25 hc
2) kill marrowgar
3) leave instance, change map to 25 nh
4) join instance
=> result: you will create a second id for 25 nh and marrowgar is spawned.

[Rushor]

kay adding this in addition:

if (mapEntry->IsDynamicDifficultyMap() && player->GetBoundInstance(631, RAID_DIFFICULTY_25MAN_HEROIC) && mapEntry->MapID == 631)
            BindDifficulty = player->GetDifficulty(IsRaid()) == RAID_DIFFICULTY_25MAN_NORMAL ? player->GetDifficulty(IsRaid()) + 2 : player->GetDifficulty(IsRaid());

        if (mapEntry->IsDynamicDifficultyMap() && player->GetBoundInstance(631, RAID_DIFFICULTY_10MAN_HEROIC) && mapEntry->MapID == 631)
            BindDifficulty = player->GetDifficulty(IsRaid()) == RAID_DIFFICULTY_10MAN_NORMAL ? player->GetDifficulty(IsRaid()) + 2 : player->GetDifficulty(IsRaid());

solves the problem for icc

but we still have the issue that we should be able to change between nh and hc during the running id

[mynew4]

SunWellCore FIX it. mapId == 631 or mapId == 724 This can refer to this
https://github.com/callmephil/SunWellCore/search?l=cpp&q=631&utf8=%E2%9C%93

[Shauren]

@mynew4 garbage hack, doing it per-mapid is NOT a solution

[Aokromes]

Anyone can takeover and finish https://github.com/TrinityCore/TrinityCore/pull/12690 ?

[Ovahlord]

Need some spiritual input from the mighty TC gods:
Dynamic difficulty seems to be acting like this:

• Normal and Heroic difficulties share a lock. Killing a boss on normal difficulty kills the boss on heroic as well. By getting a lock for 10man for example you cannot enter 25 player versions of that raid anymore.
  Trying to enter a 25 man raid with a 10 man lock will result in teleporting you to a 10 man version of your current lock.

• On retail using the switching tool inside the raid it appears that the player gets a lock for his current difficulty but not for heroic YET. Once you switch to the other difficulty you get the lock acceptance popup so you get bound to your other difficulty as well. This means that the blizzard servers use two locks at the same time to track your progression. This is probably also used to determine if players are enligible for the final heroic raid encounter such as the Lich King in ICC heroic or Sinestra in Bastion of Twilight.

So in the end the instance save system only needs to be extended to track and update two locks at the same time and force players into the same instance map once a lock has been created

[Faq]

@xvwyh any information from your side about this? Thnx

[xvwyh]

Nope. Don't know how it worked on retail servers, didn't have it implemented on my server either. Mostly because we didn't want to risk lowering the population by essentially halving the number of ICCs people could grind each week. But even if that wasn't a factor, I wouldn't even know where to start.

The only vague anecdote I've heard about dynamic difficulty switching on retail was that everything in the instance remains the same, to the point that even creatures keep their original GUIDs - if you had someone targeted before switching difficulties, you would still have them targeted after switching too. That would mean that Blizzard wasn't recreating instances from scratch but rather updating instances to new entries and stats etc. While some of it can be done on TC, a lot else is unsupported, goes against the core TC principles, or is simply difficult to grasp or find a solution for. Due to scripts being hardcoded it makes it difficult to assess what changes need to be made when switching difficulties. Spawns might be different between difficulties, what do you do with scripts if a trash pack that triggers a script magically gets more members added to it after switching to Heroic even if the previous members were already killed? What if some spawns are completely different between Normal and Heroic and Heroic-mode spawns don't have a creature_respawn record and thus will come to life even tho players have already killed them? What do you do with pools that contain such spawns that differ between modes? What if you change difficulties in the middle of an out-of-combat script with a creature that's only spawned in one difficulty? It wasn't worth the hassle and the risk of breaking stuff that worked just fine previously and nobody complained about.

[Faq]

Yeah, some feature implementation is not worth the effort.

[Ovahlord]

Uhm, fyi, Shauren already is working on a instance lock rewrite for master branch which I will eventually port back to 4.x which THEN will be easy to backport to 335.