1) Set difficulty to insane via GUI
2) Go into dungeon
3) use /difficulty normal, the game will tell you everything changed to normal
4) Look at the GUI again, GUI shows insane still
5) New spawns retain insane setting*

Before anyone says "duh" on #5, I'll use SC as an example. Load the dungeon under normal, and then change it to insane. Run over to Algor and he'll load as Insane rather than normal because he was too far away to spawn under the normal setting.

I always say: The difficulty in affected to the monsters that arent located in the parts of the dungeon you didnt explroed yet with your minimap. As soon as a new part shows up, it isnt affected by a difficulty change anymore.

The main part of the bug is that the gui and the commandline don't match eachother.

Using the map was a description of how to see different spawn difficulties on the same map. If you wanted, you could spawn a SC map on normal, kill the first two groups and then change it to insane on Algor

The GUI menu option will continue to show the difficulty setting that is 'saved' - changing difficulty via the /difficulty command only changes the difficulty temporarily. So the GUI menu option shows you what the permanent setting is, even if you've changed the difficulty temporarily.

LOL I thought this was in player guides, my bad. And thats true with SC by the way, you didnt explored the part yet at boss when killed second group, so they're affected.

So using /difficulty as a temp measure is an undocumented (well hidden maybe?) feature?

Yar, I see now. Hah. Hm. Could it be reflected when you use /difficulty then?

Oh, I'll clarify...

Currently with both ways of setting difficulty, the user is shown the same string of text. Perhaps with /difficulty it could add a temporary message. "You temporarily changed your groups difficulty setting..."