You can write your topic however you want, but you need to answer these questions:
What do you want to achieve? Keep it simple and clear!
I am trying to get rid of a annoying/reappearing “problem” in my output… on any new session of Studio.
I started a new session… with only one script (learning Scripting) … and you can see the code I have used - and that none of it calls for any " Requiring asset 1638103268".
What is the issue? Include screenshots / videos if possible!
I am aware it is not a error message (still green), but I don’t see other tutorials having the same issue.
Is it a Script bug, Studio Bug or a Plugin Bug ?
So on that, apologies if this is in the wrong section - not sure which is responsible.
I will appreciate advice on how to get rid of this annoying few lines.
Then I can see more clearly on what is supposed to be in my Output section
Thanks.
This could either be a backdoor, or an output from a Plugin, disable all your plugins and try again if it went away then find what plugin causes this, if it still exists, then check your script (or send here for me to check it).
I have around 43 plugins - so uninstalling them will be the last option lol
On the other hand - this is the script:
-- #1
print("#1 - Lesson")
-- #2
local Word = "#2 - my word"
print(Word)
-- #3
if game.Players:FindFirstChild("Roblox") then
print("Roblox is on the Server")
end
if true then
print("#3 - Value was true")
end
-- #4
function helloFunction()
print("#4 - Hello")
end
helloFunction()
-- #5
task.wait(1)
print("#5 - Hello")
-- #6
if game.ServerStorage.Name == "Hello" then
print("#6 - The server staorage has a weird name")
else
print("#6 - The server staorage has a normal name")
end
if false then
print("Value is true")
else
print("Value is false")
end
As you can see - just simple beginner lessons.
I have absolutely nothing else in Studio - just this 1 script in “Workspace”.
No Parts or Assets of any kind loaded - totally fresh Baseplate Template.
Sorry… meaning is it possible that there can be a backdoor via a plugin ?
I gather there’s just a bug in the plugin… and it’s safe otherwise (no backdoor).
