…onally identical

…monRed references

… human-readable enums rather than raw hex values

…d writing multiple bytes simultaniously, with the default length being 1

…mon Red/Blue so that data can be interacted with in a more Pythonic way

…n in the party

…tle easier to parse the data

…ability/start adding intermediate classes so data chance underneath doesn't affect API calls

…ookup

… class

Changed data folder structure from data/<data type>/constants.py and memory.py to data/constants and data/memory_addrs with files of each data type as necessary. Done bcause many data types (statuses/types/etc.) are small and don't have memory mappings in the way larger structures like Pokemon do, and making an entire directory with a single .py file containing < 20 lines felt silly.

Instead of storing move_1 through move_2 as individual instance variables in the Pokemon class, we not store them in a list of size 4 as self.moves. Each individual move is still accessible as move_n through the use of property functions, but now the list of moves can be iterated over, which makes it easier to manage cases where a Pokemon has less than 4 moves without having to manually check four distinct fields

… Pokemon class

… the enum represents

Add a function in the game wrapper to read multibyte data (in this case a pointer). this is almost certainly a feature that should either go in PyBoy proper or not exists at all (just manually reading consecutive bytes and adding them was the previous way), but it's being included here for now for ease of use and can be removed later if deemed necessary.

…lation

…y funcitons to correctly load 2 byte values

It turns out there are a couple of different ways memory can be stored in multibyte chunks (memory pointers, hex values, bcd) and there is not necessarily good indicators of which is which. To ease the burden of importing various different memory accessing functions, it's just all going back into a memory mamanger class for now

…ere not terminated on end string character

…ent first pass at Player class write to memory

… and will let us encapsulate memory data for read and write calls

…pen them outside of MemoryManager

…er wrapper functions for ease of testing if memory addresses are useful. SHOULD NOT BE PERMANANT

…n what form the memory is encoded at that address, then added overarching read and write functions that use appropriate memory type functions

…ject OR enum with MemoryAddress object as value

…y into MemoryObjects, which only store that data requested for more efficient loads/stores

…per so we have to pass less things outside of PyBoy

…ant this being commonly used

…emon-gen-1