i was making my game , and when i click test , i see a strange movement there , i check good , And for my Suprise! , it was a exploit name.
Here is:
"01:44:16.543 - Synapse Xen Script:?: Unable to find module for asset id
01:44:16.544 - Stack Begin
01:44:16.544 - Script ‘Plugin_2661950467.BlockToRoom_Plugin.BTR_Script’, Line 69 - upvalue ay
01:44:16.545 - Script ‘Plugin_2661950467.BlockToRoom_Plugin.BTR_Script’, Line 69
01:44:16.545 - Stack End"
I’m willing to bet you installed a plugin with malicious code. Remove any suspicious looking plugins.
“Plugin_2661950467.BlockToRoom_Plugin.BTR_Script’, Line 69”
Just uninstall the plugin titled “BlockToRoom” or similar and you should be good.
When installing a plugin you may accidently get whats known as a ‘Backdoor’ which allows exploits such as Synapse X who’s staff upload these malicious plugins to gain server sided access to your game.
Remove any plugins you may have that look suspect and check that scripts havent been edited or created.
What Mine685 said, the plugin that gave out the "“01:44:16.543 - Synapse Xen Script:?: Unable to find module for asset id” error was also most likely botted to gain attention of people.
Botted Plugin:
This is the example of a botted plugin,
There’s more installs than favorites, isn’t that impossible for a popular plugin?
Original Plugin:
And this, is the original plugin which still has more installs than favorites but at least there’s 7k than the 4 we have on the botted one.
I recommend you NOT installing these plugins, and firstly check those 2 numbers
(oh yea, remove the plugin that is most likely botted(aka check it’s page for the favorites number and try to find the original one.))
People use SynapseXen to hide their scripts (obfuscate) , it’s not an exploit but it can lead to a backdoor.
Why would you favorite a plugin you haven’t installed? People will install without favoriting, but nobody will favorite without installing.
Not sure why any issue with a plugin immediately evaluates to “backdoor” nowadays. The first script is a backdoor failing to load and the second one is a standard plugin script issue, not a backdoor.
The first error evaluates to an attempt to require a ModuleScript by its id. The call evidently failed because the module is closed source, deleted or in some mannerism invalid and unable to be fetched.
The second error is just a standard plugin issue. Just because a plugin errors, doesn’t mean it’s a backdoor.
Below. Misread the log.
The location of the backdoor script was in fact, inside of the plugin file.
Most plugin errors people post nowadays are related to malicious plugins failing to load their backdoors, purely because almost nothing has been done to curb the problem of backdoors, other than a closed source removal that backfired.
Check the stack begin / stack end again. It literally tells you where the backdoor is located. 
I saw it as two different errors and thought that regular plugin errors were just being perceived as backdoors when that could potentially not have been the case.
Thanks for pointing that out.
All good man. 
We all make mistakes sometimes. Lol