Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve documentation of RPG_RT chunk types #404

Open
3 tasks
fmatthew5876 opened this issue Sep 26, 2020 · 0 comments
Open
3 tasks

Improve documentation of RPG_RT chunk types #404

fmatthew5876 opened this issue Sep 26, 2020 · 0 comments
Labels

Comments

@fmatthew5876
Copy link
Contributor

Once DBString and DBArray are used everywhere, refactor fields.csv to better document exactly what chunk types are used by RPG_RT. This will allow us to extend the type system for extensions and be more explicit about what is supported by RPG_RT.

We should be explicit about defining our own library of types in liblcf, and how they map directly to RPG_RT.

  • Array<T,N> - RPG_RT uses fixed size arrays for some types. These do not have size fields. While we can and should continue to use DBArray, this allows for incompatible EasyRPG extensions such as bigger maps. If the RPG_RT type is encoded, we can detect and warn about compatibility at the liblcf layer.
  • Vector - These use delphi dynamic arrays. They have size fields, but depending on the object the size counts bytes or "objects" such as 16 bit integers.
  • Other designs TBD..
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

1 participant