Skip to content

reimplement: SHC_3BB0A8C1_0x0047A130 100%#95

Draft
TheRedDaemon wants to merge 1 commit into
mainfrom
reimpl/SHC_3BB0A8C1_0x0047A130
Draft

reimplement: SHC_3BB0A8C1_0x0047A130 100%#95
TheRedDaemon wants to merge 1 commit into
mainfrom
reimpl/SHC_3BB0A8C1_0x0047A130

Conversation

@TheRedDaemon
Copy link
Copy Markdown
Contributor

@TheRedDaemon TheRedDaemon commented May 30, 2026

Requires changes to AttackInfo: Two new field sizes set.

This one showed the shortcomings of the struct resolver:
Unlike the function resolver, which seems to be pretty good at behaving like a normal function, the struct resolver deeply effects the way the compiler handles field accesses. It required activating almost all of them to see the opcodes being produced like in the original. There is a clear difference between having the global or just a reference, no matter how stable. We always have to keep this in mind while testing around.

Also:

  • The private functions should be made public. Pragmatic reason: We can not judge visibility and we can not instantiate classes with constructor if they are private.
  • I found two struct resolvers for SHC_3BB0A8C1_0x01A279C0: In the class definition and as global. Is this intentional?

@TheRedDaemon TheRedDaemon requested a review from gynt May 30, 2026 21:26
@gynt
Copy link
Copy Markdown
Contributor

gynt commented Jun 3, 2026

The class definition struct resolver should be removed.
For the record, which class were you trying to instantiate but couldn't because of private constructors?

@gynt
Copy link
Copy Markdown
Contributor

gynt commented Jun 3, 2026

I resolved the AttackInfo.hpp thing now in a1971f3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants