Whats actualy hapening with the output

Hi there, so today I am really trying to dive deep into the rabbit hole of the console output. Now, a lot of people would say WHY?

I’m doing this simply because my friend was called stupid. And I want to make sure the reason is valid. (Also, it wasn’t me who said this to any moderators in chat, it was the dev team, RECOIL studios, the people behind Deadline, that started this curiosity) ANYWAY, let’s get to the point

With prints and warns what is happening behind the scenes in a memory perspective. Theres are two things I really want to know: the clearing of the elements, purely visual, OR is it also in memory? This may be a stupid question but as far as I’m aware, I was unsuccessful at finding a real answer

and for everyone in the comments of this post who reads it and puts yes it does clear because after 500 or so messages in the console the first ones start to disappear. Yes I know. Thats what they told us. Thats what I have seen

What have I tried myself. SImple

local Prints = 0
while true do
	print(Prints)
	Prints += 1
	task.wait()
end

for anybody who also thinks that it’s a server-client issue. it’s not, I ran the script on the client

After about 10 minutes of running this code constantly, my framerate went from 144 (my native framerate) all the way down to 25ish. How else could this happen if previous messages that were sent get cleared? The simple answer is they don’t.

So, what am I asking for here if I technically have my answer? I need to know what is or close to what is happening behind the scenes. It’s mostly validation here. Is this how it works? Are they actually clearing the memory?

I would also like to mention that this was done in a blank base plate.

It takes care of itself. Kind of like DebrisService on a delay.
The fact you are looping it so fast is causing the buildup of strings.