WHDLoad MantisBT - Beast
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0004426Beast[WHDLoad Installs Games] OCSpublic2020-03-23 17:492020-04-22 00:39
ReporterDrag0nFly 
Assigned ToCFOU 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionreopened 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
MachineA1200
CPU68030
CPUSpeed40
ChipSetAGA
GFXCardNone
ChipMem2 MB
FastMem0 MB
WorkbenchOS 3.1
KickROM40 - Kick 3.1
KickSoftNone
WHDLoad18.5
imported
Summary0004426: [ShadowOfTheBeast] Add trainer option with collision-detection prevention
DescriptionThe currently-implemented energy trainer does not work very well in this game, as the instant you touch the end-of-level tree boss (the moving skeleton-gargoyle thing) – you die.

I must have tried to pass this level 20 times at this point, without luck. The other trainers which come with the disk-based ADF versions of the game support this just fine, and in the event you do end up in an impossible situation (i.e, hanging in an abyss), the game can always be restarted.

Please consider adding this as a CUSTOM[x]=1 option. It would make the whdload experience of this game so much more enjoyable.
TagsNo tags attached.
Relationships
Attached Files

Notes
(0007963)
CFOU   
2020-03-23 23:24   
there are already an trainer added by Harry

see readme file

- Toggle energytrainer with F1 on/off. No complete trainer, its senseless:
   if you hang in an abyss you couldnt get out.
(0007964)
Drag0nFly   
2020-03-23 23:34   
Why did you close this? I referenced the energy trainer in the ticket, and it prevents one from completing the end-of-level boss at the tree-level.

This slave sorely needs a proper trainer, where one does not get killed when the "skeleton-chair" touches you.

The other disk-based versions of SOTB has this for this specific purpose.
(0008382)
CFOU   
2020-04-22 00:39   
I don't found solutions.

all found solutions cause many another trouble.

more over actual trainer is developer cheat, they are perhaps not add it for the same reason...

If another coders found a solution, he cought open again this thread and fix it...

too tme lost with that...

Issue History
Date ModifiedUsernameFieldChange
2020-03-23 17:49Drag0nFlyNew Issue
2020-03-23 23:24CFOUAssigned To => CFOU
2020-03-23 23:24CFOUStatusnew => closed
2020-03-23 23:24CFOUResolutionopen => fixed
2020-03-23 23:24CFOUNote Added: 0007963
2020-03-23 23:34Drag0nFlyStatusclosed => feedback
2020-03-23 23:34Drag0nFlyResolutionfixed => reopened
2020-03-23 23:34Drag0nFlyNote Added: 0007964
2020-04-22 00:39CFOUStatusfeedback => closed
2020-04-22 00:39CFOUNote Added: 0008382