Closed zach2good closed 3 years ago
@zach2good Can you provide an example of a good "complex" cutscene to test? Long ones I think are covered (Dawn), and for events with updates, perhaps some sort of vendor?
I pulled these categories off the top of my head, we've already covered some pretty complex CS scenarios so I think we're OK 👍
Magian trials are ok i have made Annihilator 95 :D. I reported an error on the slip storages that worked before but not now. CoP missions are ok after merge #2565 ZM missions are ok. Bastok Missions are ok.
@zach2good @claywar
RE: complex cut scenes
Both of those are heavily onEventUpdate
/ updateEvent
driven, I would call their cs events complex as F.
Corsair Rolls seems to not function 100% correct.
@TheWhaler RC'd the issues with corsair rolls. Refactoring that code a bit, and should have a fix up soon.
I cannot complete the TOAU missions because I have a problem with the mission 15 The Black Coffin. I am well teleported to the intance however once the fight is over I am not teleported out and I stay on a black screen. Moreover, when I look at my position I find myself in the water (! Pos 0 0 0 60). Then some csid are not good.
however, I don't know if we have the same problem on the release branch.
Puppetmaster attachments dont seem to be functioning. (Autorepair kit doesnt give regen to automaton)
Think I found the issue with PUP attachments (onUpdate was moved to the attachment_object table, but being called as local/global). Going to see if I can clean up some of this to make life easier.
We're probably OK to close this and address new issues as they're found :)
Since discussions aren't as supported as issues (yet!) , I'm making and pinning this issue so we can sanity check all the things that are wrong or broken in
canary
now that it's host tosol_refactor
. This is also a really good opportunity to take stock of what works in general.We've done pretty broad testing across the board as we've worked, but a focused effort would help stability a lot! This is not a carbon-copy of the "What Works" list, this is based on features that expose different areas of the codebase that have been modified. Packet handling, database interaction etc. haven't been touched, so don't need to be tested.
If you have edit power, please edit as you go :) If not, feel free to comment or ask someone else to fill in the list.
This is not an audit/balance/implementation pass! This is just to confirm things are "as working" as they were before the refactor. If there are any quick wins along the way, great, but that isn't the main goal
Base Features
Complex Features
Jobs
Recent Content
Misc