This only occurs when using Team Create and it’s been apparent ever since Team Create was first released. The main reason I am posting this is because it only ever occurs when using Team Create.
I believe it must be caused by the top bar (But I don’t know, because there is no top bar in TC?), as that pushes down all the UI. But it’s weird because you can’t see that the GUI has been lowered, only that you have to press all the buttons around 36 pixels lower for it to have any effect. Something else that’s strange is that I’ve only seen this occurrence with the plugin I use most, Build v4. If I click below a button, but where I am clicking doesn’t have any UI behind my cursor then the click has no effect, meaning some of the buttons you can’t click at all.
This is a nonissue. I’ll dismiss this as being my fault, only (though I believe it’s been fixed, so you may need to update your plugin). The issue stems from two things:
The buttons have one click detector which is actually the frame they sit on. Math is used to determine which button is clicked.
Team Create has a network, so my code expects there to be a top bar screwing things up.
The code which decides whether there’s a header now compares mouse.ViewSizeY with the AbsoluteSize.y of a frame of size UDim2.new(0, 0, 1, 0), instead of the old way of deciding on a case-by-case basis. It remains to be seen whether it will be better.
If you want to say there’s a bug, it would be that the following code is wrong.
local x, y = textButton.MouseButton1Down:wait();
print("Absolute Coordinates: ", x, y);
print("Relative Coordinates (to textButton): ",
x - textButton.AbsolutePosition.x,
y - textButton.AbsolutePosition.y); --> This is not right, but it should be.
Basically, what I’m saying is that if AbsolutePosition is measured from the bottom of the top bar, so should everything else. And I would happily see my code break again to undo this pain.
