= MH-CrystalMine =
which server: Barbies Monsterhunt World at 85.214.243.170:7777
server build: 5003
ut.exe : UnrealTournament v469e
date: 11.06.2026
map: MH-CrystalMine
#1 bug relevance (low/middle/ high): HIGH - the map cannot be completed.
description:
Mercenary6 has Event="Mover6"
Mover7, Mover15 have Tag="Mover6" and ME_ReturnWhenEncroach
Death of the “Mercenary6” will fire the event.
The player could block the door (whether by accident or on purpose).
The door a complex brush, the player could step on the edge and prevent the opening.
The door will stop opening. and both movers return to Key(0).
This unique event can only occur once.
The map cannot be completed. (This happened 11.06.2026, 19:03 CET and result: mid game map voting)
Suggestion: “Mover7” and “Mover15” should be ME_IgnoreWhenEncroach
- MH-CrystalMine_complex_door.jpg (71.61 KiB) Viewed 1271 times
= = = = = = = = = = = = = = = = = = = = = = =
The next part of the report is based solely on the original map settings, download from the https://unrealarchive.org/unreal-tourna ... c1959.html
I am not sure about recent MapPatcher values. If it has already been fixed, pls ignore my suggestions.
= = = = = = = = = = = = = = = = = = = = = = =
#2 bug relevance (low/middle/ high): LOW
description:
“Mover20” is triggering another “Mover3”
Both “Mover20” and “Mover3” have ME_ReturnWhenEncroach.
The player can anytime interrupt the mover opening.
Multiple games on this map have proven it to be frustrating,
Suggestion: “Mover20” and “Mover3” should be ME_IgnoreWhenEncroach
= = = = = = = = = = = = = = = = = = = = = = =
#3 bug relevance (low/middle/ high): LOW
description:
“Trigger0” is triggering the “Mover6” which subsequently is triggering another “Mover0”
“Mover6” has Tag="Lava-trigger" and Event="Lavadoor" and ME_ReturnWhenEncroach.
“Mover0” Tag="Lavadoor" and ME_ReturnWhenEncroach.
This is ridiculous, because the player can anytime interrupt the “Mover6” and Event="Lavadoor" will seldom fire up.
Same with “Mover0” which is a complex brush, the player could step on gate edge and prevent opening.
Multiple games on this map have proven it to be frustrating,
Suggestion: “Mover6” and “Mover0” should be ME_IgnoreWhenEncroach
= = = = = = = = = = = = = = = = = = = = = = =
#4 bug relevance (low/middle/ high): HIGH - the map cannot be completed.
description:
Same description as above.
GiantGasbag0 has Event="Skaarjdoor"
“Mover2” has Tag="Skaarjdoor"and ME_ReturnWhenEncroach.
Suggestion: “Mover2” should be ME_IgnoreWhenEncroach
= = = = = = = = = = = = = = = = = = = = = = =
#5 bug relevance (low/middle/ high): HIGH - the map cannot be completed.
description:
Same description as above.
Tentacle28 has Event="Temple-entrance"
“Mover14” has Tag="Temple-entrance" and ME_ReturnWhenEncroach.
Suggestion: “Mover14” should be ME_IgnoreWhenEncroach
= = = = = = = = = = = = = = = = = = = = = = =
#6 bug relevance (low/middle/ high): HIGH - the map cannot be completed.
description:
Same description as above.
Queen0 has Event="Titandoor"
Mover10 has Tag="Titandoor" and ME_ReturnWhenEncroach.
Suggestion: “Mover10” should be ME_IgnoreWhenEncroach
= = = = = = = = = = = = = = = = = = = = = = =
#7 bug relevance (low/middle/ high): HIGH - the map cannot be completed.
description:
Same description as above.
WaterTitan1 has Event="EndDoor"
“Mover9” has Tag="EndDoor" and ME_ReturnWhenEncroach.
Suggestion: “Mover9” should be ME_IgnoreWhenEncroach
= = = = = = = = = = = = = = = = = = = = = = =
#8 bug relevance (low/middle/ high): LOW
description:
“Trigger7” has small collision height and radius, the player can bypass it.
Its is placed just above the ground.
Suggestion: “Trigger7” should set CollisionRadius=384.000000 and CollisionHeight=384.000000
= = = = = = = = = = = = = = = = = = = = = = =