[HW][Vanu]Dailies and Story Quest #86

Merged
liza merged 7 commits from AnimaMachinae/Questionable:vanu-vanu into master 2024-10-24 14:16:26 +00:00
Showing only changes of commit 04c96efbe0 - Show all commits

View File

@ -57,7 +57,7 @@
"Action": "Buffet (Sanuwa)", "Action": "Buffet (Sanuwa)",
"StopDistance": 3, "StopDistance": 3,
"$": "0 0 0 0 0 0 --> 1 0 0 0 0 16", "$": "0 0 0 0 0 0 --> 1 0 0 0 0 16",
"CompletionQuestVariablesFlags": [1,null,null,null,null,16] "CompletionQuestVariablesFlags": [null,null,null,null,null,16]
Outdated
Review

It is -typically- enough to only include the last digit, from looking at this quest it looks like the '1/2/3' as first digit just count the completed actions (e.g. for display in UI) -- depending on which action you complete first, that will always count as [1, ...].

The last digit (16/80/112) typically represents which of the actions you've completed, so regardless of when you do the action at this position, it'll always add +16 to the last digit. This would typically just be [null, null, null, null, null, 16]

It is -typically- enough to only include the last digit, from looking at this quest it looks like the '1/2/3' as first digit just count the completed actions (e.g. for display in UI) -- depending on which action you complete first, that will always count as [1, ...]. The last digit (16/80/112) typically represents which of the actions you've completed, so regardless of when you do the action at this position, it'll always add +16 to the last digit. This would typically just be `[null, null, null, null, null, 16]`

Interesting, besides the extraneous addition of the first number, that's how I initially had it, but when testing I ended up sitting in place waiting for a state that it never reached. There's likely an issue elsewhere as well then, but I should be able to test with a different quest sometime either today or shortly after, so I'll see what's up then.

Interesting, besides the extraneous addition of the first number, that's how I initially had it, but when testing I ended up sitting in place waiting for a state that it never reached. There's likely an issue elsewhere as well then, but I should be able to test with a different quest sometime either today or shortly after, so I'll see what's up then.
Outdated
Review

The plugin only checks the parts that have any non-null value, so that would be odd.

The plugin only checks the parts that have any non-null value, so that would be odd.
}, },
{ {
"Position": { "Position": {
@ -81,7 +81,7 @@
"Action": "Buffet (Sanuwa)", "Action": "Buffet (Sanuwa)",
"StopDistance": 3, "StopDistance": 3,
"$": "1 0 0 0 0 16 --> 2 0 0 0 0 80", "$": "1 0 0 0 0 16 --> 2 0 0 0 0 80",
"CompletionQuestVariablesFlags": [2,null,null,null,null,80] "CompletionQuestVariablesFlags": [null,null,null,null,null,64]
Outdated
Review

This should probably be [null, null, null, null, null, 64], as this should only reflect the difference between now & the previous state (and 80 - 16 = 64).

This should probably be `[null, null, null, null, null, 64]`, as this should only reflect the difference between now & the previous state (and 80 - 16 = 64).
}, },
{ {
"Position": { "Position": {
@ -105,7 +105,7 @@
"Action": "Buffet (Sanuwa)", "Action": "Buffet (Sanuwa)",
"StopDistance": 3, "StopDistance": 3,
"$": "2 0 0 0 0 80 --> 3 0 0 0 0 112", "$": "2 0 0 0 0 80 --> 3 0 0 0 0 112",
"CompletionQuestVariablesFlags": [3,null,null,null,null,112] "CompletionQuestVariablesFlags": [null,null,null,null,null,32]
Outdated
Review

Similarily, this should be [null, null, null, null, null, 32]

Similarily, this should be `[null, null, null, null, null, 32]`
}, },
{ {
"Position": { "Position": {