Being that it lost in contest #11, there is a lot of work still to be done on the game.

Throughout testing the game, I've noticed that it was running a little slow, even on its fastest settings. As I haven't compared the speed of anything yet, I have know idea what would make the program run faster. Here is the source code:
Code:


Also, what do you think of the name? The first name was Arena Craft, it is now PvP Craft, and assemblybandit suggested Kill Craft in the contest forum.

Here is the beta. I've made no changes on it since the submission to the contest.
http://download1321.mediafire.com/8epiahq866qg/hpcbfgxrhrykpcv/PVPCRAFT.8xp

"Lost" is a bit of a strong word. Comments from the judges included "Loading takes a while, character is not very responsive to key presses.", "Might be better once the game's speed is up by a lot. Right now, too slow to really enjoy.", "The fact it is this far and 'works' is good, hopefully they make progress on making it a better game.", "Creative use of the homescreen and DCS color commands.", "Creative use of grays for third dimension.", and "Needs some adjustment to clarity of gameplay. For example, I often couldn't tell when I was actually striking the enemy, and when I was building/digging." Hopefully that will help you tune it.

I agree with all of the comments. I can't even play it past 2 enemies and medium terrain size, even though it's a game in itself to see how long you can last on the slowest settings before you die of boredom . It seems like almost all of the problems above could be fixed by speeding up the program. Do you see anything that I could improve that would cause a major speed increase, or is it stuck in the curse of CSE TI-BASIC slowness?

As for the last comment, I'm going to add an 'animation' for when the player or enemy takes damage in the next update.

Great concept and im sure there is room for optimisation and such. Im sure there are loads of people who are willing to help out with coding ideas.

I for one think you have done a magnificent job, remembering that you knocked this out in just a few days! .

Thanks for the complements tr1p1ea.

With its current speed, I think of the program as a turn based sandbox game. It saves the last key pressed and deciphers it your next turn, creating the illusion that the keys aren't responding. To my knowledge, there isn't much I can do to fix that issue, except, once again, make it faster.

I've sped it up a bit using labels. It's actually playable on the huge maps now. The main loop is now reduced down to this:
Code:

Even with the new improved speed, having more than one enemy is still unbearable. Any ideas?

I've compacted the the player part of the code and the enemy part into one single section. I'm currently working on bug-fixing the bug-filled code. The new code format will make adding new features much easier, such as support for older calculators and multiplayer. Also, I want to add cross-platform multiplayer, if that's even possible. Right now the only problem is that I only own one calculator, so it will be more hit and miss, unless there is an emulator that can act as 2 calculators linking with each other (jsTIfield suggestion ).

Version 0.11 released, adding a new reformatted code, fixing bugs and increasing speed a bit, and improved menus and stores. Now I start working on multiplayer and monochrome capability, after I get a better understanding of monochrome calculators and linking.

If you don't mind, some random optimizations that jump out at me:

First, a bit of a standard four-direction key thing I try to use in some form or another in the programs that require it:
Code:
to
Code:


- A*100 can be written as AE2 to save two bytes, where E is the small E meaning "*10^".
- Numbers like 0.05 can be written as .05 to save a byte.
- Statements like "If C<10 and randInt(0,2)=2" can be rearranged to save a byte: "If C<10 and 2=randInt(0,2"

Compress:
Code:
to
Code:


In a similar vein, you can compress
Code:
to
Code:


None of this will help you too much with speed, but at least you'll be able to shrink a lot of lines out of it.

Version 0.2 is released. Using the above suggestions and other techniques, I've doubled the loading speed and game speed since the first release. The newest update also adds water, obsidian, ender crystals, saving, and mining downwards.

I've decided that I won't convert this game to monochrome because it heavily relies on color features, but I'm still going to add multiplayer in a future update.

Very exciting! Keep up the good work, and feel free to continue to ask if you want help optimizing sections of code you think could be faster or smaller. I look forward to trying this new update.

Thanks, here's the code. Any help is appreciated. The code is too large to fit in one segment.
Code:

Code:

Edit:
Corrected the code for v0.21, which fixes a bug that occurred when the terrain is reloading after closing a menu, and changed the value of obsidian and the healing rate of the crystals.

I plan on adding sand in the next update, and when it gets exposed to water, it floods over. I've just came up with the code for the flooding, and it seems like it would run slowly, so I would like it to be optimized before implemented into the actual code. As well as being optimized, I would also like it to have a more random/natural pattern. The sand is at level -1 and the shallow water is at level -2.
Code:

Edit:
Added descriptions to the code

Edit 2:
Fixes the code

I think I fixed the flooding, but I can't run it because I get a memory error, even if I reset the RAM. I could get rid of ∟WATER, but I don't know an equally fast way to do 0=max(R=∟WATER by using ∟YWATR and ∟XWATR.
Code:

Edit: I've removed the X and Y list and kept the main WATER list.

How much would switching the list which have 27Y+X (WALL and WATER lists) to matrices benefit the program in speed and size?

Sorry about all of the questions, but here's a somewhat informative post about the future of this project.

Here is a list for what's going to be in the next update. I admit that it's mainly a to-do list for myself, but I'll post it so everyone knows its progress.

Code:

This game is actually pretty addictive. The most addictive and fun game I've tried so far.

The first game I tried was random enemies (I think 5) and the largest world. It's a little slow, but that doesn't make it any less fun. I'm really enjoying it.

I hope you continue to develop this for a long time. You're doing an amazing job.

Thank you, and I will continue development on it. I do regret that it is slower with more enemies, but it is a calculator after all. If you have any suggestions, feel free to post them.

I'll try and come up with some ideas, once I've played it a bit more.

The slowness really isn't that big of a problem, in my opinion. It makes it kinda relaxing.

Is this project dying? I really am looking forward to a post of "no, it's not," but its fine if it isn't. I have kind of been editing the code a little for things like color, graphics, etc and I made a new icon for it that I think looks a lot better.

idk how to add code, but if you reply, in any way, I can post the new icon. Oh, and I think the name "Blokker" or "Blokkor" would work for a new name. Thanks!



Oh, and, *SUPER BUMP*

Unfortunately, it has unofficially been halted for a long time now. Honestly, I got about halfway through the major update, and I got distracted with other stuff (like Cemetech's MC server), and I got tired of the constant memory errors, even after I split it up in 5 separate programs and optimized them.
I will try to continue the project and implement any changes that you see fit. If worse comes to worse, here is the code for someone else to continue, but for now, it would be very helpful if others could be bug testers. But I warn you, there is a lot of incomplete stuff and bugs, and it takes almost an entirely cleared RAM to play.

Download

PVPCRAFT
Code:

PVPGAME
Code:

PVPSHOPS
Code:

PVPGOTO
Code:

PVPITEMS
Code: