Wednesday, July 19, 2017

Beta 2.20 of DQ1 Remake is finally live

I have finally released Beta 2.20 of DQ1 Remake on my MEGA account, after a long time in closed beta.

Everything up to the Cave To Charlock Castle is finished (there is a monument that tells you you need to save for the next build, which will be removed in the next version). The Catilin area is fully fleshed out, as are any remaining overworld areas, save for one or two on the Charlock Castle landmass (these will be fleshed out in the next few builds).

The next build will have the normal ending implemented, the build after will implement the bonus ending, and the build after is planned to be the final build.

Unlike the original Dragon Quest, my game does not have a "bad ending" option, but it may be added in some manner by the final build.

A few bugs have been fixed in this build, including a UI bug, and a lot of legacy code and crash issues were finally dealt with. Most of this is thanks to the extremely dedicated bugtesting done by Stagefright.

And, for the following websites and groups, I have added the following characters:

Encyclopedia Dramatica: Lulzkiller (as King Kunt) (his character works in one of the banks as a LFG representative in Rimuldar)

Kiwi Farms: (Archmage) Jaimas, Lord Cipher Luna (aka Joshua "Null" Moon) and Aeterna Concordia (aka Peace and Harmony) - all can be found in Catilin, where I even tossed in some references to some Kiwi Farms memes and events.

r/KotakuInAction: HandOfBane (say hi to "The Legendary Bane" in the Catilin bank/League For Gamers branch office store)

Beta 2.20 can be downloaded here:!VM8iGYzL!pc8SDIOJ7H-aoPqDdQ3hEw

You can also find the latest copy of the game readme at the same.

Wednesday, July 12, 2017

DQ1 Remake 2.20 is getting some further balance changes before stable release

I'm now almost done with getting DQ1 Remake Beta 2.20 out of closed beta and ready for stable release, but before I do that, some issues need to be fixed as mentioned in my previous blog post. Also, the following changes for balance will be done.

1. Many more spells will have accuracy fluctuations. The original Dragon Quest games had this to prevent them from being too OP for enemies or players, and the more powerful spells and skills will have lower accuracy than their initial versions, especially multi-hit skills and spells.

2. On top of redoing the scripting for my bonus dungeon quest, the cursed and uncursed items you can get doing this will be rebalanced. Also, they will have actual gold values assigned to them to make them sellable, should the player opt to do so. I also will eliminate some items that were cloned to normalize game balance, as I was unsure where to put a few of these items several times during development, and this will be corrected for the final time before 2.20 releases in a stable form.

3. A few skills have been modified to be more useful or to fix issues with bad coding.

Monday, July 10, 2017

Nearly done with DQ1 Beta 2.20 beta testing, and some commentary on another game dev's project

This is an update for those who are following my DQ1 Remake project. The 2.20 beta has been through about ten revisions now, and in each one tons of bugs have been fixed, as I want to leave all the engine issues behind me so they do not plague me in future builds, and I want to thank beta tester Stagefright in particular.

His efforts to find and document all my numerous screwups so I could fix them have been nothing less than Herculean, and I just want to say, "Semper Fidelis" to him for all his fine work at unearthing all the fail in my project so I could fix it.

Due to his tireless efforts, the following is now no longer an issue.

1. More legacy broken code is now removed.
2. The last remaining shards of my old dialogue code should be gone.
3. A longstanding UI glitch when displaying skill data is now fixed.
4. Skills in general have received numerous fixes to damage, calculation of effect, and other fixes.
5. Tons of game crashing issues now no longer a problem.

The following needs to be fixed though:

1. Some broken transfer triggers in various areas towards the end of the game.
2. The event coding for my bonus dungeon unlock is jacked up. It was ancient code I set up in one of the earliest builds of my game, and I finally discovered it's obsolete and buggy, and due to a oversight Stagefright discovered, is prone to screwing the player out of the bonus dungeon key by mistake very easily, and thus that event sequence will be rewritten in its entirety to avoid this.

Once I have fixed all this and Stagefright confirms I've no longer fucked anything else up (won't lie, I screwed up a LOT), I will release the official 2.20 build of my game, which I plan to dedicate to the Kiwi Farms, because those guys are awesome and I even threw in a lot of shoutouts to them in the town of Catilin to show my appreciation.

And on that note, I want to mention another game dev I'm aware of named Alex Mahan, the guy who does the Yandere Simulator game, which, as I understand it, is a crippled POS he does very little work on and has numerous issues which the Kiwis have pointed out in this thread:

From what I've seen, he's a lazy asshole with some messed up fetishes, but more importantly, as a game dev, his project is an abysmal garbage heap of bad coding, bad game design, and it has been stalled in terms of actually being playable for the longest time now because it's developer is shiftless, easily butthurt over any criticism, no matter how reasonable, and refuses to humble himself and admit when his coding skills can't do what he promises and when what he has produced is frankly subpar work.

It is this I want to address him on:

Alex, as a game dev, I'll be blunt: When you get called out for producing a piece of shit, and people present good reason based on the objective quality of your work to call it shit, fall on your sword, admit it, and work your ass off. If you fuck up, own up to it and work on it, and learn to treat your beta testers with respect. Mine are a gift from God himself, and when they tell you what you screwed up, show some damned pride in your craft and fix it instead of dragging ass and getting asshurt over being told you aren't perfect.

In fact, I'm just going to be harsh: Your godawful project has inspired me to work harder on mine, and unlike you, I definitely plan to have mine fully released as a finished game before the end of this year unlike yours, and if you have any self respect, you will prove me wrong.

Tuesday, June 6, 2017

DQ1 Remake Beta 2.20 halfway done with beta testing

I'm taking a lot more time than usual to verify this DQ1 Remake build is ready for release before taking it out of closed beta, for three reasons:

1. This build will be the very last build where any scripting changes occur. The engine will be essentially complete after this build.

2. Per the first reason, this will allow the remain builds to proceed much more quickly, now that any remaining scripting work is over.

3. I now have a roadmap for eventual "Gold release per the first two reasons, as outlined here:

Beta 2.20: Everything just shy of the final dungeon of the normal route done.

Beta 2.30: Normal route finished, finished all the basics of the true route path.

Beta 2.40: True route ending implemented.

Gold Release: Assuming nothing goes horribly wrong. This version will receive any last minute polish, bug fixes, and will be the definitive build.

Monday, May 15, 2017

Another progress report on the DQI Remake 2.20 Closed Beta

After getting some more bug reports about Garinheim, I had to fix a lot of buggy tile collision issues, including being able to walk through certain portions of houses, being able to hop stair well where you shouldn't, and other wall clipping weirdness.

I should have fixed all of this.

I also got a complaint about how it looks how some landings make it look like the character is walking on the landing railing, not the floor, and I tried to fix this the best I could, but the tile art and the fact I have a 2D engine make some of this perspective weirdness unavoidable, and since I had to pay for the assets I used for the Garenheim town art, I'd have to contact the artist or someone with the same DLC pack I paid for who would be willing to modify it, as my own art skills are not that good.

I also made a few minor overworld map adjustments, nothing major, just shaved down the Hauksness and Rimuldar overworld areas a little bit.

I'm still awaiting more bug reports, but while I await them, I did make a minor story change.

Sarah is supposed to be a soldier who was detached from regular duty for personal reasons to help you, but because she's not officially on the clock, she can't use her authority as a soldier to help you until she resumes her regular post. I was informed I didn't make this entirely clear, so I extended her introduction a little and gave the player a choice to tell her you're okay with that and just grateful for the help or that you find it disappointing, both of which will modify the relationship value system I built in to the game a little bit.

I might as a few more of these altered dialogues in other areas as well, but this is the only one I've done out of necessity so far.

Monday, May 8, 2017

Closed Beta 2.20 of DQ1 Remake Continued Feedback

Got some more feedback on my closed beta and it looks like I have some more bugs to fix:

1. Seems I still have some remnants of the old dialogue system in place, need to purge that.

2. Fixing a small frameskip bug in town when picking up vegetation and eggs.

3. Complaints some music and SFX are too loud, will fix by cutting their level by 50% across the board.

4. Fix the bank, has some old code that causes graphical issues.

I plan to meticulously fix as many bugs before releasing this build, as I want the game as mechanically solid as possible before implementing the normal ending, final dungeon, and any content beyond that.

Wednesday, May 3, 2017

Closed Beta 2.20 of DQ1 Remake Feedback

I've already gotten some feedback from beta testers, and I've already fixed a lot of issues regarding UI problems, including screwed up text and number displays.

I reverted the player menu back to using the classic row format instead of the column view to fix a few more issues, but this is merely a cosmetic change.

Fonts had to be resized in several places for optimal display, and aside from a harmless "flash of unstyled content" glitch (the first character in the menu will briefly have their name and the "level' marker turn bold, then normal text), the menu is now free of UI problems, and the glitch is quite harmless for now, so I'm leaving it as a low priority to be fixed in later builds.

I have also begun experimenting with how to integrate content from DQ1 in any possible sequel, since I did have one planned, and I'm pleased to say my experiments with how to port content for us have proven quite successful, so any possible sequel, should I make one, will be able to incorporate areas from the original game in full (barring changes explicit to the sequel of course), which would be a great improvement over how most areas from the original DQ1 were greatly abbreviated in scope in DQ2.

Once beta testers finish getting back to me Beta 2.20 will enter public beta, and work will begin on the next build, in which the endings will be implemented, or such is the idea at this time.