Jump to content

ERROR client export


WASSIm.

Recommended Posts

If your client sided file has a variable storing the export, your problem will be there. Like TAPL said:

I guess that because you've tried to export but the resource client file haven't started or downloaded yet

This is also the case if you restart resource1, but resource2 still has the variable stored. The stored variable will be called to a wrong resource ( these ID's change as far as I know ). A simple way to fix this is to replace all the stored variables and just use; exports["resource-name"]:function()

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...