Home › Forums › Destiny of an Emperor › Ludmeister's Remix v3.0 Released!
Tagged: Cao Cao, Destiny of an Emperor, Destiny of an Emperor hacking, Destiny of an Emperor ludmeister, Destiny of an Emperor Mod, Destiny of an Emperor roms, DoaE, Liu Bei, ludmeister DoaE rom, Ludmeister's Remix
- This topic has 76 replies, 9 voices, and was last updated 12 years, 8 months ago by
shifter420.
-
AuthorPosts
-
June 4, 2013 at 1:22 am #8553
ludmeister
ParticipantGood evening all!
Download Destiny of an Emperor Ludmeister's Remix v3.0 (IPS patch and readme)
I am excited to announce that v3.0 of Ludmeister's Remix has just been released at my website! I've been working quite hard for the past few weeks to update it with many great enhancements that you all have coded, and then got inspired to write code myself.
Of course, the Remix is not an entirely new storyline, and does not attempt to be a full conversion; it is intended for people who might not have played Destiny of an Emperor (or have played it once) to enjoy the game with some enhanced possibilities, but not a tremendous increase in difficulty (at least, not initially!) However, I have introduced some new surprises here and there, and hopefully succeeded in adding a bit of humor. The gameplay experience is quite a bit different than previous versions, so Remix veterans will find quite a bit of new stuff to enjoy :wink: The download page above has a changelog that provides a bird's eye view of what has changed since v2.0.
As a 1MB ROM, it is incompatible with many emulators. The only Android emulator that I have found that works with it is Tiger NES, and I have not seen it on Google Play in a couple of years :evil:
Known issues: This mod only has one stable save game slot… the first one. You can play in the second one, but never stop playing unless right after you've saved at a historian! The third one… borks the game. No passing Xu Zhou or collecting 200 gold pieces. Of course, you can always use save states. It also still has the rare freeze after selecting battle orders… we haven't fixed it yet MiDKnighT :tear:
Thank you one and all for all of your work and enthusiasm in making Destiny of an Emperor all that it has become. It is an honor to work and play with you all, and Ludmeister's Remix could not have become what it is without your help:
- The DoaE Hacking Guide is instrumental.
- Niahak's Destiny of an Editor is invaluable.
- MiDKnighT's assembly chops are legendary.
- Sonic's portrait work is incredible.
- DragonAtma's font work is stunning.
I think v3.0 came together really well, for a work in progress, and I hope you all enjoy.
When all else fails... manipulate the source code.
June 4, 2013 at 2:14 am #45475MiDKnighT
ModeratorNice! I've got a lot more to do but I'll add playing this to my list. I hope you stick around. Your feedback and enhancements have been invaluable!
June 4, 2013 at 2:17 am #45476MiDKnighT
ModeratorI'll promote this ROM on the facebook page too.
June 4, 2013 at 4:44 am #45477ludmeister
ParticipantThank you MiDKnighT. :-)
When all else fails... manipulate the source code.
June 4, 2013 at 11:12 am #45478Zhuge Liang
ParticipantWhat a time to visit. With both Ludmeister 3.0 and Flames of Wu released at almost the same time. I should take time to enjoy these wonderful mods.
DoaE gave birth to Huo Hu.
June 4, 2013 at 5:43 pm #45479ludmeister
ParticipantMiDKnighT– I do intend to stay around. I'm definitely curious for feedback, war stories, and bug reports on the Remix, as it showcases a few of the new changes that you and I have introduced, and I'm very interested to see how your 255 tactics and VIT/LDR/POL work out. I will definitely want to play around with these huge enhancements as well.
Ah… and I still need to download the Destiny of an Editor code, and check it out…
Do you know what's going wrong with Save Slot 2 and 3? Is this due to the 1MB expansion? Or did I unwittingly bork something? That's a scary thought… :scratch:
When all else fails... manipulate the source code.
June 4, 2013 at 5:57 pm #45480MiDKnighT
ModeratorQuote:Do you know what's going wrong with Save Slot 2 and 3? Is this due to the 1MB expansion? Or did I unwittingly bork something? That's a scary thought…I'll check into that soon.
June 4, 2013 at 6:21 pm #45481ludmeister
ParticipantThanks MiDKnighT! I'm at a loss to know how to proceed there, since I have no knowledge of how DoaE's battery saving works.
Also, in case you are interested, I just produced a log-file that shows at least one show-stopping bug (maybe it is the only one) before a round of battle starts. I'm guessing it is a case of a mismatched RTS.
Here's a link to the log file. It's zipped, and is 528K (100,000 lines of text!) Sorry, I wanted to be thorough and show from the accepting of the last character's actions, to showing where the hang occurs (which is more of an endless loop than an actual freeze). However, 100,000 lines is much better than what it was originally (3,200,000+ lines)!
Please don't feel any big rush on either of these things, though.
When all else fails... manipulate the source code.
June 4, 2013 at 6:35 pm #45482ludmeister
ParticipantAh. I should probably give you some insight into the state of my game when it happened:
1st round of Qing Zhou (back door in cave) battle
Liu Bei/Zhang Fei/Guan Yu/Chen Deng/Liao Hua
vs.
Zhang Jao/Zhang Bao/Zhang Liang/Ma Yuanyi
Memory at end of log file (0x6000 to 0x625f):
Code:6000: 00000000000000003553000000000000
6010: 0100007E01000201061C0B0707120908
6020: 02020000000001001B6433136433340A
6030: 0B0A0000000000000000000000000000
6040: 00000000000000000000000000000000
6050: 00000000000000000000000000000000
6060: 00000000000000000000000000000000
6070: 730300070000B6010035040001010000
6080: 0B0E0B05FFFFFFFF0000000000000000
6090: 020100050306FF020100050380808080
60a0: 0080808080808000A9AAA838003B3D0C
60b0: 0D0E0F001E1914190014142819231E0A
60c0: 02030116140116040303020100000000
60d0: 0E0100006A01000082010000C6000000
60e0: A1000000F0000000A5000000B2010000
60f0: 77010000580100002F01000000000000
6100: C1E0E8000000000032C2DFE900000000
6110: 53C0DFE854000000D5E0000000000000
6120: D300000000000000C0DFE80000000000
6130: 28D5DFE8000000000000000000000000
6140: 00000000000000000000000000000000
6150: 00000000000000000000000000000000
6160: 140100007B01000086010000CB000000
6170: A1000000F0000000A5000000B2010000
6180: 77010000580100002F01000000000000
6190: 000000000000000000000000F5FCA599
61a0: 0A8C4B8D44A58F23B960E16D0AB1BCA9
61b0: C42A7C0D40504B7D0163575E37652C14
61c0: 00000000000000000000000000000000
61d0: 01000101000000000000000100000400
61e0: 00000000060606070703010200040403
61f0: 01020006080507093A00003A00000000
6200: 01000101000000000000000000000000
6210: 32000004000404000000000000000000
6220: 00000000000000000000000000000000
6230: 00000000000000000000000000000000
6240: 00000000000000000000000000000000
6250: 000000000000000000000000B1070000When all else fails... manipulate the source code.
June 4, 2013 at 7:17 pm #45483MiDKnighT
ModeratorI think that's actually a bug I just fixed which is the stack overflow bug. I think it has something to do with the A.I. bug. Anyway the fix is:
0x7A950: 0000A90E2082C468684C0080
And you're right, it is an RTS problem.
June 4, 2013 at 7:33 pm #45484ludmeister
ParticipantAwesome! I'll patch 'er up and give'r a-go. :cactuar:
When all else fails... manipulate the source code.
June 4, 2013 at 9:14 pm #45485MiDKnighT
ModeratorLet me know if you still get the freeze after the fix. This was the main A.I. problem that I knew about.
June 4, 2013 at 10:33 pm #45486MiDKnighT
ModeratorLooking at the save slot thing. Looks like save slot 3 is overwriting my page switch code that I had stuck in memory (at $7F90) hence why it's totally borked. Ideally the page switch code would be on the system page but I didn't have room for it there since the 1M ROM page switch is more involved. Looks like when you save in slot 2 it writes to $7500 then some of my code comes in later and overwrites it.
Bottom line…it's my fault and I will fix it. I need to move where I'm putting my in memory stuff.
June 5, 2013 at 12:13 am #45487MiDKnighT
ModeratorHaving a hard time finding a place to put it. I'm thinking maybe I should sacrifice slot 3 (and remove it from the menu) while keeping slot 1 and 2 in order to have a lot more memory space. Is that ok with you? Having more memory that we could use would be nice…
June 5, 2013 at 2:26 am #45488ludmeister
ParticipantI think what you're saying makes a lot of sense, actually. I think hacking out the option to choose slot 3 is totally fine; your page switch code is much more important, and makes sense to always have access to it. It will be nice to have for other functions which are very important… for instance, you could put default VIT/LDR/POL calculation stuff there, if you haven't already.
When all else fails... manipulate the source code.
-
AuthorPosts
- You must be logged in to reply to this topic.

