Be sure to send the App and all three Appvars to your calc. The Appvars must be in archive.
In order to re-adjust the greyscale you must delete the appvar GS
Oh, ok, then that is working too :PBe sure to send the App and all three Appvars to your calc. The Appvars must be in archive.
Is there some weird reason behind this? Because the GetCalc(NAME,FILE) command for reading from archived variables has also worked with variables in RAM for a while now.
I know, i just haven't gotten around adding that yet :PIn order to re-adjust the greyscale you must delete the appvar GS
Just map a key to the GTune() function. :P Alternatively, you can be a bit more bold and make your own contrast/grayscale controls, in which case I'd advise checking out the source of the GTune() function to see how to properly change contrast and grayscale delay.
Indeed but if you make copies of the data you need twice the RAM. :POh, ok, then that is working too :PBe sure to send the App and all three Appvars to your calc. The Appvars must be in archive.
Is there some weird reason behind this? Because the GetCalc(NAME,FILE) command for reading from archived variables has also worked with variables in RAM for a while now.
This game worked great fot me, apart from one bug: Sometimes when you walk past the border on the screen (to get to an other area), then immediately walk over the edge again, then you sometimes get teleported to a random location. This already happened twice to me in an hour or so of playing, but in both cases, when I tried to trigger that glitch again, it worked fine, so I haven't been able to replicate the glitch.
It doesn't seem to cause memory corruption and doesn't crash your calc, and everything works perfectly after you exit the game and start it again.
By the way, when restarting the game, does it reload from last save?Yes
That is why you can use multiple keys at the same time and "slide" accross the wall. Anyways, it might be possible if i can fit it in, currently i only have 120 bytes left :P
Also, an issue I noticed when walking around is that it's incredibly hard to get inside narrow areas. Reuben has to be perfectly aligned into it in order to get through. The Verdante Forest had this problem too. Do you think you could make the game detect those areas and have Reuben moves towards it when trying to go through?
Also, when trying to walk on a solid tile, the random enemy count keeps dropping anyway. In the original game, it only dropped when walking on floor tiles.Noticed that too but didn't think this was an issue.
Another issue I encountered is that sometimes, all of a sudden, escaping battles will no longer work, even if you try like 10 times in a row, and one of the forest enemy sometimes does 20 damage. I am unsure if he did this much damage in the original game.Blame Axe's random on that :P
Also, for the battle transition, when the screen flashes, the last row and column of pixels are not erased. You should make the flash affect 96x64 rather than 95x63.I knew i put the wrong dimensions /somewhere/ :P
Well, the issue with the random enemy count is that it can get annoying when you run into the narrow path issue mentionned just before. Until you manage to get through, you can end up having a random battle after only two or three steps. >.<Yes and Yes and good news, I just got an idea on how to re-write dynamic map stuff to free me some memory :)
Btw will the next version have a menu and title screen? (which i assume will be a tilemap with text put on it?)
Also, an issue I noticed when walking around is that it's incredibly hard to get inside narrow areas. Reuben has to be perfectly aligned into it in order to get through. The Verdante Forest had this problem too. Do you think you could make the game detect those areas and have Reuben moves towards it when trying to go through?
That is why you can use multiple keys at the same time and "slide" accross the wall. Anyways, it might be possible if i can fit it in, currently i only have 120 bytes left :P
I suck at making title screens plus I didn't really find it so ugly thus I am afraid it is the same :PWell I felt it would be best to keep the same screen anyway because it's a tilemap, so it's much smaller than an actual picture. However, if you use Horiz mode like I did for the New Game/Continue text this might not work on OS 2.53 MP and higher. However, the Reuben Quest logo was made with plenty of Line/Pxl-test for the italic effect so it might be best to make it part of the sprite sheet.
Btw, if aeTIos was to never do magic animations (since he usually disappears every 6 month or so for a long while from the community x.x), what happens to the game if everything else is completed? Would you use placeholders (such as the Illusiat 2004 magic sprites from the title screen) or would the game be delayed until next year or so?Not entirely true there lol. I usually disappear for a few weeks every summer due to me going on vacation. And I will finish the animations lol :P
You disappeared for a while during fall or Winter almost every year, though, to play that video game I forgot :PBtw, if aeTIos was to never do magic animations (since he usually disappears every 6 month or so for a long while from the community x.x), what happens to the game if everything else is completed? Would you use placeholders (such as the Illusiat 2004 magic sprites from the title screen) or would the game be delayed until next year or so?Not entirely true there lol. I usually disappear for a few weeks every summer due to me going on vacation. And I will finish the animations lol :P
Btw, not really a bug, but more of an exploit in the beta I got a while ago: If you go in a dungeon where enemies are weak enough to never hit you, all you have to do is put tape over the left arrow when walking against a wall, then you'll automatically attack when a battle occurs, so if you have good batteries, you can do like the Lete River trick in Final Fantasy VI and level up overnight while you sleep.Eh, do i really have to fix that? :P
In the original game this was impossible, because the random battle enounter count doesn't go down when you try to walk over a wall.
I think ben_g already reported me this one on IRC
EDIT: Also, I found a bug with HP restoring, when using water or cure: Sometimes, my HP loops back to 1 O.O
Also, map design bug:Nice catch!
(http://img.ourl.ca/wabbitemu-3.png)
Also, why does the screen flash after exiting your house or in the final area where there's no battle?Pretty sure I already fixed it
If that would have worked you'd have a time machine calculator, as the code for that wasn't in the beta O.O
EDIT: ALso when you beat the final boss, it goes back in the game rather than showing the ending :P
Reuben Quest: Ev Awakening
=======Installation=======
To install this game you
must send all the appVars
and the app to your calc.
It is recommended to place
the appVars into archive.
The game requires at least
4800 bytes of free RAM to
run.
=========Gameplay=========
Arrow keys: Move
2nd: Interact
ALPHA: Items and Stats
MODE: Graphic Settings
CLEAR: Exit
=========Settings=========
The first time you run it
you will be be asked to
adjust your grayscale set-
tings as they may vary
from calc to calc. After
that you should set your
delay which also depends
on the calc running it, it
defaults to values which
should be pretty close, if
not the actual correct
delay.
=========Credits==========
Programming: Sorunome
Graphics: Art_of_camelot
Story&Maps: DJ Omnimaga
Thanks to Runer112 for
making Axe!
Thanks to everybody who
supported me throughout
the development of this
RPG!
We have a website!
www.reubenquest.net
Here's a Youtube vid of the game in action:Thank you!
So far, it's near perfect, although I noted the following issues (most are minor or just nitpicking):hehe
-The first frame for the sword animation appears for a shorter amount of time than the other two. At some frequencies, it's so fast that we only see the 2nd and 3rd sword animation frame. On the regular 83+, the 2nd frame actually flickers (the entire sword flashes once so it's like if the frame showed up twice)They should all be the same amount of time as the delay is the same. It consists out of 5 frames, up, up+left, left, left+down and down
-The battle backgrounds for the 1st and 2nd dungeons are not the right ones. I don't know about the mountain nor the Ev Palace, though, because I haven't reached them yet.I pulled the ones form here: http://www.omnimaga.org/ti-z80-calculator-projects/reuben-quest-axe-remake/msg381495/#msg381495
-It would be nice if we could access the grayscale/delay setup menu from the title screen and battles instead of just on the map.Will do from the menu, battle would be too much code IMO as probably noone will ever need it :P
-The enemy death animation doesn't fill the enemy sprites completely. It's worse with larger sprites.If I made it fit in it would clear "Level up!" partly, thus I decided I'd put it like this
-There are in-game inconsistencies such as how you can exit dungeons without pressing enter, but have to press enter to get in. You should maybe make doors so that you can enter any building without pressing Enter.IMO interaction by walking onto something is only very good if you walk whole tiles at a time.
-On the title screen menu, the x2 and down arrow keys go back to the title screen the same way CLEAR does. Not that this is a problem, although this was a bit strange :PWut......that might be an Axe bug O.O
-Talking to the first guy is kinda hard because Reuben keeps moving past him. I guess I can live with it, though, since the new walking routine makes it MUCH easier to walk through narrow areas.Maybe I can add that it doesn't do that aligning with NPCs ;)
-The enemies never seem to attack first. In the original game, they sometimes did.Crap, knew I forgot something :P Do you happen to know out of the top of your head what the chance for that was?
-Random encounter rate is very high. I think in the original game it was randomly set between 10 and 30 steps after every battle, but now it always seems to be 10 or 15 (multiples of 8 pixels).I used this http://www.omnimaga.org/ti-z80-calculator-projects/reuben-quest-axe-remake/msg330930/#msg330930
-The intro scrolling animation is missing, but I don't remember if this was intentionally left out or not.Omitted on purpose :P
-When setting up the grayscale quality, if you go too low, the calc keys almost completely becomes unresponsive. Maybe make the grayscale settings so that if the user doesn't press any key for 1 minute then it exits the program?Grayscale tuner is by Runer, it is part of Graylib, so won't fix :P
-There's absolutely no indication at the start of the game stating who made the game or at least a copyright (such as 2004-2014 Omnimaga or 2004 version by DJ omnimaga/2014 Remake by Sorunome). If someone sends the game to a school friend without the readme then he won't know it's from Omnimaga. Maybe before the title screen the screen could turn black with the following text on two lines "2004-14 Omnimaga" "www.omnimaga.org".I decided to move that to the end of the game as that fit in there better IMO, but I guess I'll have to look some credits through again and add some more :P
-The readme itself misses the credits for the original sprites. Although they were converted by Art of Camelot for the most part, almost all enemy sprites were originally ripped from Final Fantasy II and III for the NES (Square-Enix). It also doesn't state that I made the original 2004 game. :P It might also be a good idea to include a link to Omni in the readme since the original game came from here (although it came from Epic Programming Studios but EPS has died long ago so...) and put a download link for the beta on reubenquest.net :PSame as above :P
I might have forgotten some stuff but that's what I could find so far. Most of those are mainly nitpicking, though, and minor issues, except the wrong battle backgrounds and very high encounter rate.the game
EDIT: Wow I didn't realize this post was this long O.OHehe :P
I've found a bug:Wut, Level 15 is supposed to be max O.O
when you've reached level 16, your maximum hp is 14...
this makes the game impossible to play
that might explain why my max hp is 14...I've found a bug:Wut, Level 15 is supposed to be max O.O
when you've reached level 16, your maximum hp is 14...
this makes the game impossible to play
It doesn't have to show up for very long (1-2 seconds?)...just the rho with "Omnimaga: 2014" underneath. I think it would look a bit cooler with the splash.-There's absolutely no indication at the start of the game stating who made the game or at least a copyright (such as 2004-2014 Omnimaga or 2004 version by DJ omnimaga/2014 Remake by Sorunome). If someone sends the game to a school friend without the readme then he won't know it's from Omnimaga. Maybe before the title screen the screen could turn black with the following text on two lines "2004-14 Omnimaga" "www.omnimaga.org".I decided to move that to the end of the game as that fit in there better IMO, but I guess I'll have to look some credits through again and add some more :P
Fixed this in my local version :)that might explain why my max hp is 14...I've found a bug:Wut, Level 15 is supposed to be max O.O
when you've reached level 16, your maximum hp is 14...
this makes the game impossible to play
I'll see if i can fit it in :)It doesn't have to show up for very long (1-2 seconds?)...just the rho with "Omnimaga: 2014" underneath. I think it would look a bit cooler with the splash.-There's absolutely no indication at the start of the game stating who made the game or at least a copyright (such as 2004-2014 Omnimaga or 2004 version by DJ omnimaga/2014 Remake by Sorunome). If someone sends the game to a school friend without the readme then he won't know it's from Omnimaga. Maybe before the title screen the screen could turn black with the following text on two lines "2004-14 Omnimaga" "www.omnimaga.org".I decided to move that to the end of the game as that fit in there better IMO, but I guess I'll have to look some credits through again and add some more :P
what are you supposed to do after returning the shovel?Explore and find out what to do :)
On an unrelated note, was the beta uploaded on TI-Planet and ticalc.org?No, only omni and cemetech.
93+SE/me wantz :3
Ah ok, do you plan to upload the game there when it's complete, tho? It would gain more exposure (I could upload the TI-Planet one when ready if you don't have an account, since we are allowed to upload anyone's program there it seems), especially considering Omnimaga doesn't have a proper download archive anymore.On an unrelated note, was the beta uploaded on TI-Planet and ticalc.org?No, only omni and cemetech.
I only planned ticalc, i kinda forgot tiplanet <_< I have an account there, though :PAh ok, do you plan to upload the game there when it's complete, tho? It would gain more exposure (I could upload the TI-Planet one when ready if you don't have an account, since we are allowed to upload anyone's program there it seems)On an unrelated note, was the beta uploaded on TI-Planet and ticalc.org?No, only omni and cemetech.
Also back to bugs: It seems we cannot cancel magic selection. Once you enter the magic menu, you can't go back to the main battle commands: You are forced to waste a magic spell. IIRC, in the original we could cancel with ALPHA.You could cancle that in the original game? lol, never knew that. i'll add that then.
I don't know it for sure but it may be this:what are you supposed to do after returning the shovel?Explore and find out what to do :)
Hint: try to get to areas you haven't been to before ;)
(when playing the original game the first time that part took me hours to figure out, lol)
Yeah, as a reminder, Reuben was originally described as a puzzle-RPG, so there's quite a bit of exploring to be done when you see something special and fewer clues. ;). In the sequel, the only real puzzles are pushing blocks around, though.Woooooops, it still stores the string for the water thing, though, but never calls it aparently :P
EDIT: ANother bug: When you interact with the fire pillars, it tells you you need fire to melt ice instead of water to unlit fire. ???
Also, when you took down the fire with actual water, the water remains intact in the bottle. I didn't see if it happens with the fire too, but just pointing out.Ok, maybe i should say that I didn't really test the game a lot :P
EDIT 2: Another bug: The very rare enemy in the final dungeon (the one with 15 level that gives 255 experience points) has a weird line of pixels through it. Corrupted sprite data?Yeah, probably corrupted data, may be because i builded all those things on my calc which was having some flash corruption. I should build everything on another calc >.<
EDIT 3: Also, it appears that the fire item ignores elemental weaknesses. I think a similar bug was present in the original game, but normally the item behaves exactly like fire, but is supposed to do twice as much damage (meaning four times more damage than regular attacks if done against an enemy weak against fire)I thought it was supposed to be that way O.O
Oooh I see. I guess I can live with it if it's not dangerous, though. It doesn't seem to cause any harm other than a few display issues when scrolling the MEM menu. :P I was just making sure you were aware of it.According to runer it is safe :P
Also, if you want I could help you update the readme later because the current one might need some extra info, including known bugs (at least the ones that won't get fixed)Yeah, that would be awesome, i won't be here this weekend (including Friday), though >.<
That is a known bug, due to abusing L2 as a whole buffer, and there is no way around fixing that except getting rid of double-buffering and thus have it flicker all over the place or by using up 768 more bytes of user ram which is IMO not worth it.
still giving that bug >.<That is a known bug, due to abusing L2 as a whole buffer, and there is no way around fixing that except getting rid of double-buffering and thus have it flicker all over the place or by using up 768 more bytes of user ram which is IMO not worth it.
Try using ClrDraw(L2+103) before exiting.
still giving that bug >.<That is a known bug, due to abusing L2 as a whole buffer, and there is no way around fixing that except getting rid of double-buffering and thus have it flicker all over the place or by using up 768 more bytes of user ram which is IMO not worth it.
Try using ClrDraw(L2+103) before exiting.