wtfNeedSignUp
kiwifarms.net
- Joined
- Dec 17, 2019
This sounds like a fun calculation. Mind you the following can be optimized further:
Suppose we have 1024 different items in pokemon and each one has maximum of 99, so that means a total of 1KB memory for items (each item being a byte).
For Pokemon you need to save level and 6 stats, let's say those are integers (4 bytes) as well as moves and items which can also be a integers (4 bytes). So overall 48 bytes per pokemon. Saying you have 6000 pokemon then that's 6K*48B = around 288KB.
So overall disk space is 289KB, multiply it by 4 if you want redundancy, around 1MB.
Mind you, it's GF so they probably have Yandere Dev level programming where moves are saved as strings rather than references. Making memory cost skyrocket.
Edit: Forget to multiply the integers by 4, also you'll need an identifier for the Pokemon (another 4 bytes) and probably want a linked list storing them which is an extra 4/8 bytes per pokemon. I did forget adding the Pokemon names which can be just as expensive as the entire data (16 unicode characters that is around 48 Bytes). Still under 3MB with all the changes.
Last edited:
