-
Notifications
You must be signed in to change notification settings - Fork 42
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
Extend functions.yml format #453
Comments
Since the current website document stuff is from your previous "better docs" pull request, feel free to make another one. |
Sounds like a good idea. |
I gotta say I don't like deprecating vanilla opcodes. For compatibility I try to use as much vanilla stuff as possible, so 99% of the time, |
For If the opcode gets "fixed" (i.e. returning valid object pointer for inactive hand slot), you will break the vanilla game as at least For Not sure about this one, I think it should be fine to fix the vanilla opcode (thus make |
Well, the field can be called somehow else, it doesn't matter. |
I have a suggestion to further detalize function data by splitting
detail
into separate fields.That would allow to provide signature help:
The format would change like this:
old
new
The proposal is only to allow this format, not to convert everything at once, hopefully that can happen naturally over time.
Another thing I'd like to suggest is to allow an optional
![Captura desde 2023-01-24 12-24-29](https://user-images.githubusercontent.com/1279852/214218220-ff3b660e-0b57-4b39-b18f-1a60292b27ff.png)
deprecated
string field, which could be used to do, well, deprecations.The text was updated successfully, but these errors were encountered: