10 replies to this topic

[genesis]

1. Put the main loop of your program at the beginning (e.g. gameplay for games, calculation for programs) because most commands start searching at the front of your program. An example if you don't belive me is in programming. Press Top and Bottom and you'll find Bottom takes longer. To do this, place Goto * at the beginning of your program and Lbl * with all your title screens and options at the end. I did this in Secret of Aan and the character moves twice as fast!

2. Use Locate mode where possible if using CFX (ignore those AFX users!!!). It is much faster (and someone see if Graph mode is faster on 9850 G cause I had one for one day and it was so fast!!! Locate mode has the scroll option and the only con is bad graphics but good text.

3. Look out for alternatives for saving memory. A certain part of your code can be shortened. For example, all commands like Mat#[*,*] don't need closing brackets. Find out where *+1->* can be replaced by Dsz. Although cheap, see if the text your displaying is a programming code (e.g. Locate). When modifying a matrix or list file a lot, convert it to a variable first and then covert it back later. Try not to use colour unless it is easier to understand as it is decoration for memory.

4. Don't list instructions and storylines in your program, no-one reads them and they are a waste of memory. Be like Street Fighter and list it in a HTML document for all to read (Mac and <{GNULINUX}>).

5. Try not to draw too much in your program and draw using the least commands possible. The appreciation of them is overshadowed by the memory taken up and the speed. You can use many commands to replace what you have drawn. You can use F-Line's and Text (like Joker's Wild) to replace pictures.

[Pixter]

Maybe Crimsoncasio can make a tips and tricks section in his tutorial and add your tricks

[CrimsonCasio]

1) this is true, but if you do as I have said in another post (and will be in my tutorial) if you split everything up into diffrent programs then all parts of your code move at fast speeds, increasing the total game play speed considerably. plus, its not just that searching starts at the top, its also that with every byte in the program it gets slower, try typing at the bottom of a 10000b prog, its not fun... worse yet, try scrolling up.

2) use both in tandem (see lesson 8 of my tutorial) both have their uses.

3) I agree with everything you said here, except not to use color, on the graph mod color is very useful, since it is layered orange pixles are at the top, then green, then black/blue, this means that black pixels overwrite nothing but other black pixels so you can make a background in orange and green and your character (in black) can move about freely.

4) in RPG's storylines can be nessicary, put them in a seperate text file to prevent clogging up your programs.

5) on drawing, the only command you must not use is circle, it is increadably slow. if you must draw a circle create your own code to do so:

for 0->D to 360 step 15 // ~30
plot sin D, cos D
Line
Next

[BiTwhise]

1) This is true only for labels and gotos. For, While, and Do loops push their offset onto the stack so no searching is required

5) To plot a circle (or a box, or a triangle, or some other shapes as well) you can use Paramtric graphs.. that is usually faster

[genesis]

Wow, you guys are experts... I may have added some of that stuff but I those are my main techniques. Plus, I got disconnected. And with the programming thing, THAT'S EXCACTLY WHAT I WAS GOING TO POST.

I'm sick of all those reviewers on the Internet complaining about too many programs in for one game. Someone creates a whole program for you and you don't even have the decency to scroll a bit without complaining!!!

[Casto Productions]

Multiple files are ok, but I don't like to get carried away with it. I use a lot of Do LpWhile loops and things like that because Goto Lbl loops are impossibly long with the way the calculator searches. To me, it seems as though the calc searches downward in the code from the Goto command, and if it doesn't find it down, then jumps to the top of the program and searches from the front down. SLOWWWW... Multiple programs help quite a bit, but just be sure to name the extra programs properly, like starting them with a "~" or something because I know I always have programs on my calc that I don't feel like searching for just to use.

[CrimsonCasio]

in my tutorial there is a section called good programming techniques which covers this kind of stuff.

by the way all contributions are welcome...

[rjstephens]

3) Shouldn't that read +1-> can be replaced by Isz? And also, Be REALLY CAREFUL!!! Isz usually isn't a problem but i have had countless errors with Dsz because it was 0.

For the hollow-heads here (you know who you are) If a variable calculated with Isz or Dsz =0, then it will skip the next comand. This can create problems.

[BiTwhise]

think everyone understood what he ment. and he also said "Find out where *+1->* can be replaced", implying it can't be replaced everywhere (as you said, if the statement results in 0, the next command is skipped, which can useful)

and, please don't call ppl names, like hollow-heads..

[huhn_m]

@rj:

I don't know ahy you are so mad the last days but i don't like it if one calls me
tempered of who I think isn't better then me. I didn't know the fact that
ISZ/DSZ skipps the next command if result is 0 but you also don't know
things I know (for sure!) but you don't have to scream your anger for
anything out by insulting other ppl.

[CrimsonCasio]

yeah rj, there are lots of people here who could justly call you the same thing ( ) but dont. you seem to be acting strangely latley, just cool it otherwise action might have to be taken. also if your speaking sarcastically clarify your meaning with a or or the like.