Introducing, a first look at what I want to make into a full game: Bejeweled 84+!

Click on the image to jump to the latest version!



As of now, it just loads the graphics, creates a random board with no match checking (yet), and displays that board.

If anyone's wondering how I did all that, one word: textsprites.

Download here or here. Tell me what you think!

EDIT: Source code for the curious (processed with TokenIDE):

Code:

Pretty cool! Are you using hybrid or regular basic?

I'm gonna be using pure TI-BASIC for everything, hopefully. At this point, it is all pure TI-BASIC.

Also, I'm testing a system of generating boards that have no matches before you start.

Your text sprites look really great there. I think I've only seen Elfprince13 and perhaps Bsparks use text sprites that effectively before, so I salute you for going that route. Keep up the great work, and I can't wait to see how this progresses.

Thank you so much. It took me a while to manually convert the images to text and type them in on my calculator XD

Bump.

New code and binary! You can now switch gems! Match checking will come later.

Press 2nd on a square, and the corners of the selection box will turn black. Press 2nd on that same square to deselect, and an adjacent square to switch them. If you press 2nd on any other square, it deselects the selected square and selects the new one. So, basically like the CSE version



Source code for the curious:


Code:


Download here or here. Tell me what you think!

Bump.

Newer code STILL! After 3 days of work, it is now possible to actually match gems, and play like a regular Bejeweled game! Levels and points will come later



Source code for the curious (I myself think it's messy, but it works! and well at that!):

Code:


Download here and here. Tell me what you think! Also, test this to your heart's content, as this now has the main game mechanics!

Why is it that text sprites work on the monochrome calculators? When I ran it on my TI-84+CSE just to see if the text sprites would work, stuff kept getting covered up with white, so it didn't work at all.

How textsprites work on the monochrome calculators is that each character has a certain pattern of pixels on their leftmost side. For example:

Code:

has (from top to bottom) 10000, and

Code:

has (from top to bottom) 01110.
These are displayed right next to each other (I mean by the PIXEL), and each left-hand pattern is drawn from left to right to create an image.

For example, this code on an 83+ or higher will show you how a donut picture is made (press ENTER to see it draw character by character):

Code:


My program doesn't work on the CSE or CE mainly due to 1. the coordinates for drawing them being different, and 2. the different fonts of both.

Text sprites are possible on the CSE and CE models, but requires some coordinates adjusting. This is how JWinslow23's game looked like when I tried spacing out each ASCII character by 1 pixel instead of 1 and changed the text Y location:



Unfortunately, the CSE adds gaps of white pixels both at the top and bottom of text rather than just the bottom, so you can't use text sprites to create large sprites in height, since there will be a white gap between each row of characters.

One concern, while we're talking about the game's overall design: I'm not sure that putting the PopCap logo on it is a great idea. While it's a respectful way to acknowledge the original publishers of the game, it also appears to imply that you're affiliated with PopCap and have permission to use their logo, to me. I would recommend removing it.

Noted. No PopCap logo in the next update, just the jewel.

My progress on game-over checking:

* My List►Matr hack didn't work out
* Using augment({0,0},seq(sum( instead of the long augment( line is 10 ms slower.
* Typing out 10^ for small integer powers is actually faster than using the 10^( token, by a couple of ms. This should save ~20 ms per iteration, but not as much as precomputation would.
* I'm still trying out algorithm changes, but I don't know if anything can be faster. Your implementation in two pieces instead of fourteen has motivated me to optimize as much as I can.

EDIT: The augment(seq( was slow (73 ms), but unrolling it is only 31 ms, which saves about 30 ms net, and at the cost of only 8 bytes. Here's my current code with timing:

Code:

Bump.

This is almost a full game now! I just need to optimize some stuff (maybe) and add game saving.

Any testers of this new game are welcome. I tried a bold font on the Game Over (or, more correctly, "NO MORE MOVES") screen (but it's not in the screenie), hope it looks cool.



Source code for the absolutely insane:

Code:


Download here. Tell me what you think, and please notify me of any bugs, glitches, or feature suggestions!

Bump.

This should be the finished product right here! I implemented saving games, as well as restarting your current level and restarting your entire game. There's also a logo for DoorsCS7!



Source code for the masochist:

Code:


Download link here. Tell me what you think!

Congratulations on finishing and releasing this game! I'm suitably impressed with how quickly you put it together, and how complete it seems to be. Do you have any future plans for it? From what I've heard, you've been busy debugging and de-glitching it over the past 24 hours.

I don't have that many future plans for it...that is, unless I figure out how pure-BASIC textsprites would suitably work on the +CSE

Seriously, if I figure out how to do that, then I'll do a color calculator port. Until then, though, I have no future plans, except optimizing it more if I find any.

Code:

As for the first optimization, that means you're adding the L₁≠L₂th element of L₂ . That's an INVALID DIM error for me most of the time.

As for the second one, I'll add that in, but make sure to test it.

Sorry, I meant (L1+(L1!=L2)L2; my intention was to only add the elements of L2 if they're different from those of L1.