This does not address all the comments I left on the prior PR.

Thanks for the quick feedback.

I tried to address the points from the prior PR as follows:

• used the PR template (including AI disclosure/checklist),
• created a clean branch from upstream/main with only related commits,
• introduced set_offsets3d(...) for Path3DCollection and Patch3DCollection (no 2D->3D round-trip through set_offsets()),
• added check_figures_equal tests for post-creation set_offsets3d() and set_array() updates on both collection types.

If I am still missing one or more of your prior points, could you please point out which specific ones are still unresolved? I am happy to revise.

• This does not cover all the 3D artists and would not fully close mplot3d: set_offsets()/set_array() don't work right for 3d collections #784.

Thanks for clarifying.

I updated the PR description to mark this as a partial fix (no longer claiming it closes #784).

For follow-up coverage, could you point me to the specific 3D artist classes you want included in this PR? I can extend it accordingly.

Could you first please clarify if you are using AI assistance to write your comments here?

Yes. For comments, I use AI only for translation/grammar because I'm a Brazilian Portuguese speaker and wanna communicate clearly in English.

The technical reasoning is mine: I reviewed the code changes myself, ran the tests locally and I can explain each change in detail. I also disclosed AI assistance in the PR template. :)

Ok, translation is fine.

We would want to bring this in for all 3D artists at the same time, so that there is consistent behavior. We would also want to include get_offsets3d functions or similar to mirror the setters.

I also do not understand the purpose of the array modification tests, could you please explain why those are needed?

Thanks for clarifying.

Understood on consistency. I'll revise this PR to add a consistent 3D offset API across all relevant mplot3d artists, including a getter counterpart (get_offsets3d or equivalent) for each setter.

About the set_array tests: I added them because issue #784 explicitly mentions post-creation set_array() behavior (including color-update problems), so I wanted a regression check while touching the same classes. The intent was to guard existing behavior, not to broaden scope.

If you prefer this PR to stay strictly on offsets APIs, I can remove the set_array tests and keep them for a separate follow-up PR.