MH-Wolf

[Buggie]

Conversion for MonsterHunt this map:
https://unrealarchive.org/maps/unreal-t ... e95bb.html

Shot00000.jpg

Shot00001.jpg

Shot00002.jpg

Shot00003.jpg

Shot00004.jpg

Shot00005.jpg

Shot00006.jpg

Shot00007.jpg

Shot00008.jpg

MH-WolfV0.7z

[Buggie]

Shot00009.jpg

Shot00010.jpg

[OjitroC]

Certainly converts well to a MH map

Had two or three of these in the log

Code: Select all

ScriptWarning: Counter MH-WolfV0.Counter0 (Function Engine.Counter.Trigger:018E) Accessed None 'EventInstigator'

[Barbie]

Had two or three of these in the log

Code: Select all

ScriptWarning: Counter MH-WolfV0.Counter0 (Function Engine.Counter.Trigger:018E) Accessed None 'EventInstigator'

That counter counts died monsters. Maybe the monster was destroyed between raising its event on death and the processing the event by the counter.

[Buggie]

Monster killed by something which not pawn. So EvenInstigator is None. Typical when monsters killed by mortar or mover.
In upcoming v469c this warning fixed.

[OjitroC]

Monster killed by something which not pawn. So EvenInstigator is None. Typical when monsters killed by mortar or mover.

So could get that scriptwarning if a monster is killed by an auto-cannon? Which is what might have happened though perhaps a monster fell into the vacuum zone?

[Buggie]

TeamCannon is Pawn. v436 with VacuumZone not show this message. But if monster killed by placed projectile (same as mortar do) - yes.

---

Automatically merged

There mortar at the end of map. So when it blow up monsters this warning happen.

[OjitroC]

The screen shaking from the firing of the 'big guns' makes this map unpleasant to play after a certain point - in my view, the shaking is excessive - I don't know what other people think but it would be nice if it could be toned down somewhat. I must confess it became too unpleasant for me to continue to play (the hundred or so tentacles in the big gun area seemed somewhat OTT as well ).

Not directly related to this map, though it does occur when playing it, but is it possible to get rid of these messages which flood the log

Code: Select all

ScriptWarning: MonsterHunt MH-WolfV0NC.MonsterHunt0 (Function Botpack.TeamGamePlus.FindPlayerStart:0443) Accessed None 'PlayerReplicationInfo'
ScriptWarning: MonsterHunt MH-WolfV0NC.MonsterHunt0 (Function Botpack.DeathMatchPlus.ChangeName:0085) Accessed None 'PlayerReplicationInfo'

[Buggie]

It is challenge, not easy walk with weapons and monsters.
You can fast run and disable cannon. Possible with die.

This messages come from UT bug, when SkkarjTroopers turn to "players" and script not able get their PlayerReplicationInfo.
https://github.com/OldUnreal/UnrealTour ... issues/415

[OjitroC]

It is challenge, not easy walk with weapons and monsters.
You can fast run and disable cannon. Possible with die.

You could run fast, sure, if you could see where to run to (and, of course, if you know the cannon can be disabled). I'm sure it would still be a challenge even if it didn't shake so much as to seriously disturb one's vision. Oh well, not a map I'll play again.

[sektor2111]

Not directly related to this map, though it does occur when playing it, but is it possible to get rid of these messages which flood the log

Code: Select all

ScriptWarning: MonsterHunt MH-WolfV0NC.MonsterHunt0 (Function Botpack.TeamGamePlus.FindPlayerStart:0443) Accessed None 'PlayerReplicationInfo'
ScriptWarning: MonsterHunt MH-WolfV0NC.MonsterHunt0 (Function Botpack.DeathMatchPlus.ChangeName:0085) Accessed None 'PlayerReplicationInfo'

This would be the X-th discussion toward monster going bIsPlayer, just for touching a stupid weapon - complain at Epic for this flood or... use a fixed MonsterHunt.