- Joined
- Apr 22, 2013
- Messages
- 37
- Reaction score
- 35
- First Language
- English
- Primarily Uses
- RMXP
(I waffled if this belonged in "tutorials" or "maker-specific"--please move if necessary, mods!)
So I've only been using RMXP for thirteen years or so and I really ought to know this by now, but is there an optimal tileset length for XP? Of course they can go on forever, but I've read that longer tilesets can slow things down. Is there a rule of thumb for how long is "too long," or does it depend as much on the player's computer as on the game itself?
For example, the tilesets I'm working with all fit the same formula of pieces (ie, four floor tiles, two wall types, two bed types, two blanket types, two table types, more-or-less the same kind of table clutter, and so on.) To help me keep track of them while I work, they're currently all in one document, about 2500px long. Is it generally preferable to have a smaller number of tilesets for the program to keep track of, or more tilesets with less information on each?
I've been deliberately holding off on mapping anything (besides color tests) so it's not like I'll have to redo any maps--but if I don't have to split it into half a dozen different sets that are 50% similar table clutter anyways, that would be delightful.
So I've only been using RMXP for thirteen years or so and I really ought to know this by now, but is there an optimal tileset length for XP? Of course they can go on forever, but I've read that longer tilesets can slow things down. Is there a rule of thumb for how long is "too long," or does it depend as much on the player's computer as on the game itself?
For example, the tilesets I'm working with all fit the same formula of pieces (ie, four floor tiles, two wall types, two bed types, two blanket types, two table types, more-or-less the same kind of table clutter, and so on.) To help me keep track of them while I work, they're currently all in one document, about 2500px long. Is it generally preferable to have a smaller number of tilesets for the program to keep track of, or more tilesets with less information on each?
I've been deliberately holding off on mapping anything (besides color tests) so it's not like I'll have to redo any maps--but if I don't have to split it into half a dozen different sets that are 50% similar table clutter anyways, that would be delightful.
Now my randomly generated maps check for collision errors, and move stuff around in real time if they finds any. 
