fix: fix goofy goober code Yamato didn't proofread

[Someone-193]

Description

Describe the changes
some dude PR'd some async safe code for CR cuz he thought events were async and causing a crash so he rewrote CR spawn code, this just makes it synchronous again (cuz SL is synchronous) while still maintaining the rewrote spawn code

What is the current behavior? (You can also link to an open issue here)
Unnecessary async safe code + a field that should be a property

What is the new behavior? (if this is a feature change)
code is cleaner and likely more efficient

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
no, but I bet the PR this is fixing was 😝

Other information:

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentations

Submission checklist

• I have checked the project can be compiled
• I have tested my changes and it worked as expected

Patches (if there are any changes related to Harmony patches)

• I have checked no IL patching errors in the console

Other

• Still requires more testing