[nit: "Block based" is not specific to procedural style. • Snap! can do functional too. It has lambdas, some higher-order builtins (keep items _ from list _), custom blocks can even look like "C-shaped" custom control structures reveiving the nested body as a lambda; even call/cc continuations... • OOP too: Sprites are stateful objects. There is builtin properties like position visibility size etc. but also variables can be made per-instance. Sprites can be cloned, with prototypical inheritance of properties. In Snap!, i know sprites can also be composed in a hierarchy, with position orientation and size being relative to parent - similar to Morphic's structural reification. • OOP in message-passing sense: Scratch uses message passing for coordination between sprites, but it's limited. Snap! has more, plus "ask/tell to execute this code in your context" instead of named methods (Screw encapsulation 😜) but none of this answers your Q]

I'd say Factorio fits your description well, what with both data and behaviors reified in the world? But what's the paradigm? 🤔 A lot of "conveyers and pipeline oriented programming" -- which sounds like dataflow, and doesn't capture nuance of behaviors also being mutable, destructible etc. And whats the paradigm of Baba Is You?