 [ Tile Engine v3.0b ] 
 

 Program: Tile Engine 3
    Type: Graphics demo, Rpg starter thingy...
    Date: 6.18.98
  Author: Tek / neozones@geocities.com
          www.geocities.com/~neozones

  Be sure to unzip with the -d parameter in pkunzip, or else the tiles won't
 load!

  Okay, here is Tile Engine 3.0b. As long as 50 million people in the QBasic
 community are making rpgs based on tile engines, they may as well have
 something strong to go off of, or look at.

  Unlike some previous versions of Tile Engine, this one is now fully
 commented in every regard so that even the newest programmer might just
 understand. Tile Engine 3 uses 66% less memory than v2, although, I left
 one major optimization out: numbering tiles. So, you could index them and
 upkeep would be a snap, but for the sake of getting the tile engine idea
 down, I left that out.

  The tiles were made with n!Media v.40 (unreleased), but they'll work with
 any version of n!Media (v.05 & v.12), and hell, even Tile Editor might
 let it work.
 
  I've been looking at ways to speed this thing up, and there's a few ideas
 I have... they include, a different PUT routine (Blast lib or something),
 or hey, why not asm... also, it may be using some more time than it needs
 on calculations, but it's still good.
 
  This program uses a new idea I thought up (which other people probably
 thought up too), about walking and not being able to walk on tiles. Why
 track a separte variable for them, when you can just make the tile a
 negative number for walking = false? It saves memory, which is good, and I
 suppose that in it self makes it more efficient.

  This is by NO MEANS what you should/have to do, I just know that some
 people don't know what to do, or end up rewriting half of their code. I also
 know that some people have much better rpgs that are more simple than this.
 This is meant to get people on their feet, if they need that extra help.
 Even my rpgs don't look like this (optimized to do less work, and uses the
 Blast! Put routine), but people might be happy as is, and in any case, it's
 small, to the point, and efficient, as far as I care. Good luck, and happy
 programming.

 [ Disclaimer ] 

  No responsibility is assumed for the (mis)use of this program, and/or it's
 associated files. You have been warned, although, nothing's gonna happen
 that's bad unless you do something stupid (like throwing your keyboard out
 the window because something won't work for you...)



