quince3800

Wasn't there a version of this series that had actual defensive backups and nickel, dime packages on a 32-team rom? I've looked several times for this. Did it get taken down?

View File random rosters, from original 2D (3-4 4-3) This is an NES rom I made by ordering a "draft" and selecting the most rational team-building strategies I could think of for all 28 teams. I got bored playing seasons with regular rosters and decided to do something to make them more even. The draft order was drawn up to be as even as possible. The rom also has some hacks (upped INT thresholds, HP blow up hacks and Bruddog's push/pull hack + others). It's just to have some fun with. Submitter quince3800 Submitted 05/05/2018 Category Tecmo Bowl - NES

meaning they reset into the RS ==> RP into MS function/equation?

This may be a meaningless note: @29bcf you can swap certain bytes to generate the INT sequence with the defender having the ball (I'd gotten this to partly work with 109e, but I can't duplicate it now; others go to the INT sequence, but freeze the game: 779d, 959d, e99d, 519d).... I'm wondering what the jump to bytes are for the 29DD5/29DE4/29DF3 sequnce. Could this be inserted into the @29bcf location? Probably not because these seems to control something about going to whatever calculation is employed when the ball is in the air. When the 10 9e swap was working (it had multiple times previously, but now it won't...???), players were grabbing INTs on regular passes from a solid distance away--like maybe 5 yards--so this seems not to be a viable answer, but that location will glitch during a tip drill session if you change it. (I have a state saved to test). You can also make players jump for the ball (won't repeat now--the code/data logger had been open) or make the game go to the jump for an INT cut scene (af9c, which still works, but anytime the ball is in the air it does this and it's not a natural pass sequence, plus changing the first byte gives different scenes) or to the FG cut scene. It seems like the code isn't naturally made to permit this via one small change though and I can't read what's happening.

Greetings, Someone asked me about setting kickoffs to automatically become touchbacks when they go into the endzone. Using Bruddog and Xplozv's information I was able to figure out that setting @25108 to 205790 and @25117 to 207090 achieves this. However, the game freezes at this point and won't loop back to game play. (The screen goes black after the touchback animation and stays there). Fixing this is over my head. Does anyone know how to get this done? Take care. Edit: if the change is to 4c5790/7090, then this will work, but then every time you go into the endzone it's a touchback. @24114/2489c control what happens when the ball carrier is tackled.

@Bruddog: you posted the same location twice

Dude, Tecmo play calling works like this: @4410/44410 is a first set of 11 pointers (22 bytes, and 16 in hex). This corresponds to play 00 (a left+a bottom run). for every successive 22 bytes, you move forward (so play 01's pointers start @4426/44426) these pointers call up locations in the @8000-9fff range that tell the players what to do (you reverse the pointer and subtract 1ff0 in hex of 8176 as a decimal) Thus, you can't just switch slots (00, 01, etc.) because the code (the combination of 11 play commands for each player) that's being called up is linked to that particular play. What you did was tell run 0 in play slot 0 (referring to the Play Maker) to behave as run 0/4 (play 14) against up+b, run 0/5 (play 53) against left+b, run +/6 (54) against right+b and as play 55 against down+b. Some of these are top runs, whereas the original play was a bottom run. Also, the formations differ, so the results you're likely to get will be all over the place--the players will be maybe running a shotgun play from the pro set formation (think Jerry Rice running his slot route while flanked out at the bottom of the screen). maybe you could copy and paste play numbers, but they have to share formation and play direction otherwise, you can't have all 64 plays available at one time... if you want to edit reactions, you'll have to change pointers in the strings mentioned above (for defense play 13 begins @61b2/461b2) in order to change what the player is being told to do

I wanted to ask before I got too far into this: Is it possible to move the play command sections to @a8000 and @b8000 respectively and then just have basically all of the space you want? In a previous post (in the HP as diving topic) Bruddog said: "NES MMC3 mapper can only have two banks loaded at a time. The bank this hack is in runs from 0x28010 to 0x2C010 on the acutal ROM file. Also for JSR's the only valid ranges are 0x8000 to 0xBFFF. 0xC000 -0xFFFF is the fixed bank in memory." I'm thinking that if all banks are 4000 bytes long, then the logic of what I'm thinking is off because if you wrote too much code, then it'd no longer fit into the prescribed bank. Writing a variable for a play to jump to another area seems way too complicated; simplying having a lot of extra space (if possible) would get the same thing done, no? I'm starting to read some things on ASM commands and bank switching, but it seems that what I thought (@a8000/b8000) maybe isn't doable. Also, I'm looking at the trace material from a 4-3/3-4 rom, but referring to offensive commands.

This hack can be made to pass where the QB makes a choice as to whether to pitch (and/or likely handoff also) or to go into the passing command. I haven't gotten much into the other similar command, but from Xplozv's College Demo rom you have: C1 28 C8 D9 94 04 33 32 31 F5 42 B8 FF 32 B8 C1 3A 3C before a string that calls it up: @9750: CC FE ED (jump back 12 hex spaces from FE to the beginning of the above text) @9753: CA 51 B7 (pointer to the FE loop command @9751; does the CC belong to the above?... presumably, yes) ... D5 (shotgun snap; this could change) CB 00 F8 | 01 (pitch to RB1 after following the YY, XX path) DE 00 01 (interval over which the QB can pitch) FF 32 B8 (stand forever) Note that the pointer is 43b7, which gives @9753, so you have to call it to the right spot, otherwise the QB just falls down immediately after taking the snap. Also, all of the 1X 00 FE EA man series commands have to be written out, as is noted above. If not the defense will take control of the ball after 10-12 seconds into the play. I haven't figured out what constitutes a good pitch sequence, but you have to D7/D8/D9 the back over the LOS after receiving the pitch (I have F3 28 | D9 90 01 | DE 08 10 | A4 | FF 32 B8 right now--I don't know what the A4 is doing), otherwise the RB will become the QB. (As of right now and if you wait to pitch, then the RB will still act like the QB though). There may be another way of doing this (or not because it seems that Xplozv had a similar thing going on), but I don't know of it yet. There's another similar code @96cb that reads: C1 55 D2 D9 94 24 43 32 31 F5 42 B8 FF 32 B8 C1 05 19 (CC?). What follows @96DD is: (minus the CC, which is included just above) FE ED | C1 0F 19 | FD E2 04 | E3 04 | D8 CC F0 | 27 38 B8 | FE D2 | D4 | C0 00 DC | E4 | 2C 03 B7 | C0 00 E0 | F0 80 | C7 FD B6 | C1 5A D2 | D9 (=?) | 93 54 42 31 | F3 42 B8 | FF 32 B8 I'll pick this apart later. Also, note that I took the @28000-2C005 sequence from Xplozv's rom in testing, which he edited, but it seems not to matter which version (his or Jstout's) you use. I still don't know where you can move Jstout's tapping hack or the no fumble after TD hack though. You can't move them to the blank space starting @2FEF0 or @2CF50.

The code for this @28000-2c005 overlaps with numerous other hacks. Is there a way to change this?

Where is this screen coming from? Are these just your notes on the side or is this generated by a program?

There's something different that happens here when the player catches the ball in the endzone. I'm trying to create plays and I noted a WR fumbling immediately after a catch in the endzone a few weeks ago. I just now checked the code. It's the same (I used ctrl+f). It's in a different location (@2bf74), but the jump command is 4c 64 bf, so that shouldn't be a problem. I don't know if the stats were changed because I was testing and it's was a preseason game. Just a note.

I tested it, but I didn't take any notes. That code is correct: C414FCFFE0FEFAFF, where C4 14 can be C4 XX. That leaves you with only one other C4 command, although you could overwrite one of the C5 commands, which start @9f63 (see the @4ee8 range). Doing this does not cause the game to misattribute TD values; that I've tested. However, it does cause the player to run forever after reaching the endzone--unless he catches the ball in the endzone, in which case he'll just hold his arms up forever. The grapple effect works until the point at which the defensive player goes into his C5 command; then the ball carrier becomes transparent to that particular defender. (The onset times for the C5 commands are straddled and for some reason sometimes don't go into effect. Thus, you don't have to change the defensive in-a-funk commands on the bf60 line). The change allows you to meet an oncoming defender at the goal line and engage in a grapple or be grabbed from behind/the side while crossing. It causes no other type of glitch, however. The celebration pointer slot starts @4e10/44e10, which is correct and only the last byte (so @4e26) actually controls the ball carrier. And you do have to call the pointer to hit the beginning of the grapple command (i.e., the FC) and not the C4 command. (Mine starts @9f59, but the pointer is 4b bf). I haven't been able to figure out how to stop the running forever thing; I think that's over my head and I stopped trying. What you can't do is set up another C4 command in front of the above code and then change the FE FA to FE F8 (or other). That will make the player go look for someone to grapple with once he crosses the goal line. I tried about everything I could think of here and the above was the only thing that worked. This is separate from the defensive (and punt return?) touchdown celebration, where the code begins @bf61. This is controlled by a string of such pointers starting @76e8/476e8, but I haven't check to see which is which--there's 60 hex bytes of code calling up the celebration pointers. Changing the offensive code won't affect INT return TDs.

Your reply is over my head a bit. I understand the words you're saying, but not what's required in order to get it done. I'll have to sift around to see what I can find out. As for the number of plays, it's however many I can legitimately get in right now. There are 115 play slots available, which means hot routes on blitzes, etc. (Apparently there are more on defense too, but I haven't tested it). Does is make a huge difference if I have more than 64 plays? I probably will actually have towards that number, but I haven't finished planning yet.