-
Notifications
You must be signed in to change notification settings - Fork 799
[proposal] Lua setup for spells, abilities, skills. Rework AoE properties definition. #8933
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
base: base
Are you sure you want to change the base?
Conversation
| UNBRIDLED_LEARNING = 0x04, -- Requires "Unbridled Learning" or "Unbridled Wisdom" for access | ||
| TABULA_RASA = 0x08, -- Requires "Tabula Rasa" for access | ||
| MAIN_JOB = 0x10, -- Only available if obtained from main job current level | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add a "job point" requirement aswell?
|
Seems like a thoughtfully designed proposal in my opinion. I have captured hundreds of hours of content in the past few months and it seems obvious to me that barring any server performance issues this should be the way foward. The game just quite literally does not handle target finding and AOEs in general the same way as LSB right now and this would be a huge step towards era accuracy. Not to mention the accessibility from a developer standpoint to implement the hundreds (thousands?) of commented out skill IDs in the SQL. Having a majority of the information centralized into the lua would go a long way in speeding up that process. |
|
Hi all, I'm still getting use to the FFXI code and may not understand the full extent of how the code maps together so, I'm sharing my point of view. From a testing standpoint, I personally find Lua a lot easier to work with, especially when iterating on While debugging Here’s an example of the kind of output I was seeing during testing: TFDBG output (click to expand)Having clearer and more explicit targeting and AoE definitions in Lua feels like it would make this stuff a lot easier to reason about and debug, and probably help cut down on special cases in Also am happy to help where I can to move this forward. |
|
This PR has been automatically marked as stale because |
I affirm:
What does this pull request do?
Not for merging.
I started typing out a long essay on where this is going but I'll defer for a little later.
All you need to know is Targetfind needs to be slightly rewritten to eliminate hacks but before that can happen the way targeting is defined needs to evolve to clearly separate targets from AoE-affected entities.
Since targeting is a major part of these SQL rows, we may as well just pull in all the information and reduce the SQL to just ID/name - that is very much a stretch goal and doesn't need to happen at the same time as AoE definitions.
Proposal
Introduce various
onXXSetupreturning a """strongly typed""" table sharing 75% of their definition between all type of actions.I have included examples representing most cases, there are very likely some edge cases I haven't addressed at this point in time.
Key benefits:
Possible cons:
Alternatives:
All of this is highly tentative - I can't really start working on targetfind itself until I know where I'm going with AoE definitions.
Steps to test these changes