Quick answer: Bug bashes with only engineers miss design and audio issues. Cross-functional bashes (design, audio, art, narrative present) surface different bug classes.
Engineers find engineer bugs. Designers find design bugs. Same game; complementary signals.
Invite each discipline
Engineer, designer, audio lead, artist, writer. 90 minutes; specific focus.
Rotating tester roles
Designer tests audio; audio tester tries narrative. Cross-pollination surfaces blind spots.
Discipline-specific reports
Each discipline's reports tagged. Easier triage; clearer ownership.
Share findings broadly
Each discipline learns from the others' findings. Knowledge spreads.
“Cross-functional bashes find the bugs that fall between functions.”
If you only have engineers in your bash, you'll only find engineer-visible bugs. Invite the team; the signal grows.