If you look at my initial example, the two consoles are, in fact, being placed in different containers, and yet the problem still occurs. Also, a quick check shows that while the consoles are reporting a changed font size, the containers are not. (Also, for the sceptical, hiding the containers indiv...

I get the same thing happening when I create a Label via Geyser. So it seems to be one of the more generic functions that is causing the problem.

Well, I have narrowed it down some, but I can't dig around inside of Geyser, so it is somewhat limited. This line triggers it 100% of the time, for me. local test1 = Geyser.MiniConsole:new({name = "test1"}) But this line doesn't. (I thought it would be worth ruling out the functions that would in th...

I just made a quick alias that demonstrates the problem very clearly, I think. Here is the code. local test1 = Geyser.MiniConsole:new({name = "test1"}) local test2 = Geyser.MiniConsole:new({name = "test2"}) test1:setFontSize(8) display(test1.fontSize) --> 8 test2:setFontSize(10) display(test2.fontSi...

They do, and they have unique names and positions. The objects are all created and function properly, I just left out the extra details that don't seem to be important.

But as soon as a set the font size for any miniconsole, all of the miniconsoles show that new value as their font size.

So, I double checked, and with my current profile, it does, in fact, happen every time I raise the sysConnectionEvent, likely due to something else that I have happening in response. Since things are still fairly simple on my end, I could track down the line that triggers it, if you want.

I'm checking the "fontSize" variable associated with the window. To cut out all the stuff in the middle, here is basically what is happening. chat.window = Geyser.MiniConsole:new({name="chat_window"},chat.container) chat.window:setFontSize(8) affects.window = Geyser.MiniConsole:new({name="affects_wi...

So I ran into a new issue with word wrap. I have several miniconsoles up at once. And one of them uses font size 10, while the others are using font size 8. The ones using font size 8 are set up first, and then the other one. But as soon as I set the font size for the new console, the variable stori...

All of your stuff will remain, yes. There have been some changes since then though, so it is possible that some things may no longer work if they use functions that have since been gotten rid of.

Ah, yes, scrolling up and down does fix it. Seems like a rather strange bug. It doesn't always seem to follow the sysConnectionEvent for me, but it happens a lot.

Thanks.