Hmm, well, the easy parts will be making the tools for tilemaps and sprites. To view, say, inventory menus, Grammer's Menu(' command will be very handy.

As for storyline, maybe a classic hero quest? Badguy happens, hero is summoned to save the day, hero has various struggles/trials to get to the Big Fight.

Hmm, well, the easy parts will be making the tools for tilemaps and sprites. To view, say, inventory menus, Grammer's Menu(' command will be very handy.

As for storyline, maybe a classic hero quest? Badguy happens, hero is summoned to save the day, hero has various struggles/trials to get to the Big Fight.

I agree with the tools. I'm in the process of making a sprite editor where I can just use augment to add another sprite to the sheet and sub to take one away. Plus I'm making a tilemap editor. I think I'm going to put the sprite data and the tilemap data all in the same appvar eventually. My only question since I've never dabbled with screen scrolling is how do I screen scroll. Does Grammer take care of all of that for you? Because if I display the tile map and I scroll the screen, do I have to redraw the tile map and will the tile map be shifted?

As for your story line idea. I'm thinking about making it a post apocalyptic game with cool password cracking quests and having to gain clues to access more parts of the map. All while fighting bad guys. The hero could be a popular person. He could be part of the new world illuminate who took over after all the governments fell. I don't know. I write poetry. Lol. I think I was ranting.

I'd just make a very generic storyline at first. You should focus on getting the engine working before worrying about making an interesting story. Make sure you know what kind of features you want first (like chests, special scripted events etc)

Yah. The easy part will be the engine. The harder part will be using logic to identify what things are available and what things aren't. I'm thinking I'll have to use some type of appvar for the logic. Like how flags work. If a bit is on then this feature is active, etc...

Grammer has a screen shifting command. I just don't know if it shifts the tile map too.

I know how screen shifting works. I just don't know how to draw the tile map when the screen gets shifted.

Screen shifting only shifts the data on the screen (and for reference to E37, right/left shifting can shift multiple pixels at a time and is optimized to take advantage of bytes and nibble shifting).

The tilemap routine draws the map to the screen. When you shift, you have to tell Grammer to draw the incoming tiles afterward.