Listening to field changes in a table (OOP Object Replication)

You’re trying to solve a problem caused by a design choice, and not the design choice itself. Consider if you actually need the server and client to keep an object with synced properties, and what use would this have? Maybe what you’re trying to achieve is possible via a more idiomatic approach.

Here’s a similar thread, with an underrated reply: How Do I Work With Remote Events In Modular OOP? - #3 by IdiomicLanguage

2 Likes