"Tables cannot be cyclic" error only in online -- not play solo

I’ve created an OOP system and I pass some of the OOP objects via remote events directly from server to client. On the other side of the bridge the associated object is determined by object reference (e.g. model in game).

I’m getting a “Tables cannot be cyclic” in the F9 debug menu, which is odd because in studio the error does not occur.

Does anyone have any experience with this?

1 Like

Somewhere your table is referencing itself. Look at your variables, and where they are used.

Any advice on doing that where there isn’t an issue in play solo but there is in online?

I don’t know without code, you should consider posting some of it so we can assist you better! :slight_smile:

1 Like

We tell you anything about it unless we see the code.

Found the cyclic table. Apparently studio doesn’t catch this problem.

Did you try using Test Server? Play Solo is a strange hybrid between server and client so I tend to stick to Test Server when messing with server-client interactions. It may be that Test Server would’ve picked it up.

1 Like

This is a bug

This error will not occur in studio or test servers, only online.

1 Like