Well, I guess that my game now contains the core mechanics for tactics rpg (Except AI). I want to know what are the mechanics that you like in tactics rpg. Things that I will implement(By priority): 1.AI 2.Combat animation(I'll do something similar to Half-Minute Hero battles on the top screen) 2.Ability to select and play other stages. 2.Inventory system. 3.Config 3.Skills. 4.Unit managment.

J3A83J3Y

This is the key: J3A83J3Y. I can't upload an image of the game without mods because currently I'm charging my 3ds. As you can see, the tall red and black cannon are new and there are other stuff like coins that kill you when you touch them and more blocks can be put over rails(! blocks, firebar, note block and more).

Probaste la ultima version? tiene cañones que pueden disparar enemigos.

Also with 'industrial Sprite' I meant sprites or texture with industrial thematic. English is not my native language D:

Lowerdash is not too difficult to learn because kldck_hul have uploaded a lot of documentation and tutorials on SmileBasicSource.

I translated most of the text for v3.0 with google translator(Its not perfect but is something) but then v4.0 came out and i had to start all over again.

Note that he is using the version 3.0. The last version has better performance than that.

This is the top screen for now. Here is the key for the people who want to see it: A: Select B: Back L+R: Menu KEY:[KKJAEGD]

I use this code for some animations. What it does is receive a button constant(Ex: #LEFT) and restore animation values for that. Then, it store the animation on an array and run it if the array isn't empty. Finally I store the button on the anim% to knew what is the current animation. The part that is missing on the function are labels and end: @UP DATA 10,11,-1 ... END

Could anyone help me? I need industrial sprites(mostly tilesets) to submit this game into SmileBasicSource's programming contest but I'll not have too much time to do the assets. Also, which one is better? Lot of unit on screen but few designs for each one or lot of design but few units on screen.

You need to change the file jumpdx_sp.grp. Then, the changes will appear on the game. To change the size of the sprites you must modify the code but I'll not explain that because it's too complex.

Also, define milestones for your project. If you have a big project then you should use them to feel that you're doing some progress. I shouldn't recommend long breaks. Probably, you will forgot what you're doing or your goals and then you'll lose interest on the project.

Can you post the key?

I haven't seen a program like that yet. I know one that's called rune wars(A game similar to advance wars). Also, I'm trying to make a game tactic rpg. It's not finished yet but I have a stage editor, menus and movement of the units. If you want, I can post the key.

Those are the sprites defined with SPDEF. If you call SPDEF number,X,Y,W,H then it will change the one in that number with image in coordinate (x,y) with size W,H of your sprite sheet. By default, all unused sprites are defined with SPDEF N,0,0,16,16.

Thanks, my progress has been slow because I don't use too much time to program on my 3DS and I try to be careful with the code structure. I need to change the sprites to use this on the "End Of The Year" contest on SmileBasicSource but first I'll try to finish the basic stuff for tactics gameplay: -Turns -Basic attack(No Skill/Item) -See stats for each unit. -Win/Lose condition.

You should start to learn how to program with the following topics: make a "hello world", usage of variables and arrays, control structure and functions definition(def).

There are a lot of options: 1. There are tutorials on SmileBasicSource(Check the tutorials written by randomouscrap) 2. PetitProfessor have uploaded some tutorials on Youtube. 3. The digital manual that comes with SmileBasic (Ingame help is also useful but the digital manual is more complete)

15)Use goto only if you want to simulate switch case. For everything else use other control structure ( while...wend, repeat...until, for...next, etc) 16)Don't use gosub. Use a function created with def instead. 17)If you won't use an array anymore, then clean the memory used by it. You can do this with pop, unshift or by assigning an empty array to that variable.(GC will do the magic)