TheGamesDb.net

Ideally speaking, the app should draw from its own mirror, with API calls limited to syncing actually new data. That way, single-use "full syncs" could be used to bring the apps current, then API calls could keep them current, without forcing end-users to sync the entire site on every new ...

If you're not using arrays because of the app structure, that's something we can consider for the per-key limits. Right now we're mostly shaking out the bugs and globally curtailing excessive use, but in your unique case, they do sound a bit low.

The current monthly limit is 1000 queries, with 20 calls per query allowed, for 20000 total calls.
That's 20000 basic entries, or 10000 entries with screenshots and fanart.
We'll be considering app-key limits on a case-by-case basis once those are fully implemented.

160 calls per day by that logic, each request can process 20 calls.

Taking all that into consideration, a bitmask may be appropriate for, say, different Ratings systems. Beyond that, perhaps a timestamp check is in order, so identically stamped fields are returned using the slightly more monolithic format to save calls. Something for the future, at least.

Just a quick note, per my understanding, each request can return up to 20 game listings, so 20000 from 1000.

No they aren't, they're separate regions, and we're already stretching things by having Genesis and MegaDrive separate.
A separate format would be the Famicom Disk System, which has an entry.

If you click where it says "Front" below where the artwork should be, it's still there. http://legacy.thegamesdb.net/banners/boxart/original/front/55766-1.png http://legacy.thegamesdb.net/banners/boxart/original/front/55766-1.png This is a side effect of the restructuring for v2 (beta here...

It's totally acceptable to add Flash games to the PC category.

These are technically Arcade systems...