Skip to content

Conversation

@SnarkAttack
Copy link

This pull request is meant to add two major features to the Pokemon Generation 1 game wrapper:

  • Enums/constants for many important values, including IDs of Pokemon, sprites, moves, items, etc., and then relevant mapping to names/other features, to make code more readable.
  • Classes that encapsulate data accesses to avoid requiring users of the wrapper to look up their own memory addresses/manage multiple data accesses for what is functionally a single data structure (e.g. a single function call to access all of a Pokemon's data)

Maciek Baron and others added 30 commits June 27, 2020 19:09
… 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
…ability/start adding intermediate classes so data chance underneath doesn't affect API calls
SnarkAttack and others added 29 commits November 8, 2023 14:55
…ent first pass at Player class write to memory
… and will let us encapsulate memory data for read and write calls
…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants