nesdev.org

I was thinking of using 8x8 tiles to make more flexible graphics but that would be more time-consuming, and take up more space for maps, but I might be wrong.

I know some techniques to save space like color cycling, palette swapping, sprite flipping and mirroring. Are there other tricks among these?

I was thinking of dividing into 2 KB for the common tiles, 2 KB for the status bar and 4 KB for the rest of the tiles. With an MMC3 mapper this should be possible.

When a game has tiles that might be reused anywhere, do you have to copy them for each tileset or can you have dedicated banks for this?

I've posted a pic with such graphics that currently takes up 64 tiles.

I've posted a few mockups which are mostly screens. While I don't intend to make it an actual NES game, I'm not exactly sure how many tiles you can store in a ROM, assuming it's 256 KB. As for the game, it consists of 50 levels including boss fights, but unless the levels take place on a single scre...

Here are tilesets for a NES-styled game I'm working on called Treasure Rush. It's a platformer in which you explore levels to find hidden treasures.
It's currently a work in progress, I'll post mock-ups to show the tilesets in action.

While FamiTracker lets you store up to 64 different songs, I don't know if that limit applies to NES games as well.