We agree it's not a good way. But it's how the stereotypical OOP project will implement it. The other way I'm familiar with is implementing rocket audio render

We agree it's not a good way. But it's how the stereotypical OOP project will implement it. The other way I'm familiar with is implementing rocket audio rendering at a central location (where also sheep and houses audio rendering is implemented). That's the data oriented way. But the "drawback" is that one then needs access to the "raw" rocket data (one could still do it with a Rocket class, but would have to make a very complicated data-getter interface). Not very OO. Thanks for your friendly reaction to my criticism, by the way.