Leaderboard

Revisão de banimentos não estão mais sendo aceitos.

numTable = {} -- insert table.insert(numTable, 10) table.insert(numTable, 8) table.insert(numTable, 2) table.insert(numTable, 6) table.insert(numTable, 4) -- sort table.sort(numTable) output: 2 4 6 8 10 as provided before: https://www.lua.org/pil/19.3.html

Hello, may this help you? https://www.lua.org/pil/19.3.html

-- Define window dimensions and background image path local windowWidth, windowHeight = 480, 320 local bgImagePath = "lgn_bg.png" -- Calculate window position to center it on the screen local screenWidth, screenHeight = guiGetScreenSize() local windowX, windowY = (screenWidth - windowWidth) / 2, (screenHeight - windowHeight) / 2 -- Create the window (invisible, we will draw the background image instead) local window = guiCreateWindow(windowX, windowY, windowWidth, windowHeight, "", false) guiSetAlpha(window, 0) -- Make the window fully transparent -- Create GUI elements local backgroundImage = guiCreateStaticImage(0, 0, windowWidth, windowHeight, bgImagePath, false, window) local usernameLabel = guiCreateLabel(50, 80, 100, 25, "Username:", false, window) local usernameField = guiCreateEdit(150, 80, 280, 25, "", false, window) local passwordLabel = guiCreateLabel(50, 120, 100, 25, "Password:", false, window) local passwordField = guiCreateEdit(150, 120, 280, 25, "", false, window) guiEditSetMasked(passwordField, true) local loginButton = guiCreateButton(50, 160, 100, 30, "Login", false, window) local registerButton = guiCreateButton(190, 160, 100, 30, "Register", false, window) local guestButton = guiCreateButton(330, 160, 100, 30, "Guest", false, window) -- Show the window with the background image guiSetVisible(window, true) -- Ensure that the window is destroyed when the resource stops addEventHandler("onClientResourceStop", getResourceRootElement(getThisResource()), function() if (isElement(window)) then destroyElement(window) end end) -- Add event handlers for buttons (implement your login logic here) addEventHandler("onClientGUIClick", loginButton, function() local username = guiGetText(usernameField) local password = guiGetText(passwordField) outputChatBox("Login clicked. Username: " .. username .. " Password: " .. password) -- Implement login logic here end, false) addEventHandler("onClientGUIClick", registerButton, function() local username = guiGetText(usernameField) local password = guiGetText(passwordField) outputChatBox("Register clicked. Username: " .. username .. " Password: " .. password) -- Implement registration logic here end, false) addEventHandler("onClientGUIClick", guestButton, function() outputChatBox("Guest clicked.") -- Implement guest login logic here end, false) Try this

To take away some confusion, understand that the changes being announced here are mostly focussed on cutting out the 'community front' of AC team operations, so that we can optimize limited manpower and rebalance expectations for our users to accept there will be periods we can't make waves, if you were able to move yourself into our perspective on how people always want everything solved, fixed, sorted out immediately on their whim, and how persistent they are in that (and in most cases bring something misconceived/invalid, after which they can't even be convinced otherwise or that would take from our time disproportionally), you'd be straight out scared and quickly stressed out. OP was clarified by adding in this segment 1 day after the topic was made: We will continue to bring AC improvements and get rid of emerging cheats and cheaters, but at our own pace, without external pressure or too high community expectations, from now on everything is on a best-effort basis and the point is that there may be periods during which we can't make any waves due to manpower constricts. You can see that this topic intends to lower your expectations and respect the amount of free time we (as volunteers) are able to invest, and get off our backs for things being different compared to some years ago. We're also OK to restrict ban appeals and player reports so we can delegate all of the manpower that's left on our new strategy, breaking cheats (patching them) and just preventing them from working to begin with, instead of permanently banning cheat users and having to deal with them "regretting" in ban appeals. We are also OK to restrict reporting cheaters as our focus shifts to breaking the cheats, and to get the required information to break one, we have our own methods and channels so much that we don't need any sort of reports. Due to the state of anticheat and heuristics, we always have a good picture of abnormalities and what cheats are doing, so the main limiting factor is manpower to get to work with what we have & know. After all, cheating on MTA will not be left alone, and AC team will disrupt it and raise the border even more whenever manpower allows it to do so. Cheaters should realize that their fun may come to an end at any unexpected moment, and that if they're too used to being able to cheat, they will be very upset to have to adapt to playing normally for as long it takes the cheat devs to catch back up to us again.