Other Lists > Steve's List Forum

Top 5 Suspicions I'd Like to Confirm in the DK Code

(1/3) > >>

stella_blue:

* Does an active hammer, and the point at which it will expire, have any influence on fireball behavior?
* See item #1
* See item #1
* See item #1
* You know the drill by now.  Do I really have to type it again?

LMDAVE:
I love trying to figure out code without even looking at code.

Given when you do get a hammer you usually see fireballs change to a "scare" mode, now towards the end of the hammer the hammer starts flashing, so there is obviousy a flag/timer that knows this point to tell it to start flashing, my "guess" is that same flag that starts the hammer flashing also releases the fireballs from "scare" mode.

danman123456:
It HAS to have an influence on the fireballs. So many times on the barrel stage right when the hammer is going out the fireball decides its time to climb up the broken ladder on the right and try and trap me on the 5th girder. It does it so much there HAS to be so logic in the code for it to just be random.

hchien:
I swear the fireballs run away from you as soon as you grab the hammer on rivets (especially the first/mid-left hammer).

Actually I don't really believe that, but it does seem that way.  My bet is the hammer has no influence on the fireball AI-- it's all in our heads.  But I'm willing to listen if anyone does a code analysis.

Jeffw:
I've read the fireball algorithm and there was nowhere that I saw in which the hammer status has an impact on fireball behavior. Specifically, the probability of reversing direction appears to be fixed at 50% for each decision point and not dependent on hammer status or anything else. Similarly, the decision of whether or not to climb a ladder also appears to be fixed at 25% probability when it is moving right (but 0% when moving left) as long as taking the ladder is permitted but not forced.

There are still two possibilities in which hammer status could have an impact on fireball behavior. The first is the possibility that the programmers put the code for this behavior is some other area of the code outside of the fireball AI routine, which is unlikely. The second possibility is that there is a bug that causes hammer status to affect fireball behavior. While it is possible for such a bug to exist, in general behavior that is both complex and coherent is unlikely to be produced by a bug. In this case, the behavior described by both Dave and Dan is complex in the sense that the fireball behavior would require knowledge of where the fireball is, where Mario is, which direction is towards Mario and how long before the hammer expires and would need to affect each of the 5 fireballs individually in order to produce the appropriate behavior. The behavior is also coherent in the sense that it is behavior that might have feasibly been intentionally programmed in. So with this in mind I think you can have fairly high confidence that behavior like Dave and Dan describe does not exist.

Navigation

[0] Message Index

[#] Next page