Attempt to call global a nil value ошибка

What Are Lua Errors?

A Lua error is caused when the code that is being ran is improper. There are many reasons for why a Lua error might occur, but understanding what a Lua error is and how to read it is an important skill that any developer needs to have.

Effects of Errors on Your Scripts

An error will halt your script’s execution when it happens. That means that when an error is thrown, some elements of your script might break entirely. For example, if your gamemode has a syntax error which prevents init.lua from executing, your entire gamemode will break.

Lua Error Format

The first line of the Lua error contains 3 important pieces of information:

• The path to the file that is causing the error
• The line that is causing the error
• The error itself

Here is an example of a code that will cause a Lua error:

local text = «Hello World»
Print( text )

The code will produce the following error:

[ERROR]addons/my_addon/lua/autorun/server/sv_my_addon_autorun.lua:2: attempt to call global ‘Print’ (a nil value)
1. unknown — addons/my_addon/lua/autorun/server/sv_my_addon_autorun.lua:2

That is because Print is not an existing function (print, however, does exist).

The first line includes the path to the file that is causing the error — addons/my_addon/lua/autorun/server/sv_my_addon_autorun.lua

Afterwards, the line that’s producing the error — sv_my_addon_autorun.lua:2 (Line 2)

Lastly, the error itself — attempt to call global ‘Print’ (a nil value)

Below the error, we have the trace of the function. Simplified — If the error is inside a function/chunk of code that is called from somewhere else, it will state where the code is called from.

If the error happens serverside, the text color will be blue. If it happened clientside, it will be yellow. If it’s menu code, it will be green (not a typical scenario). Messages which look like errors but are colored differently, such as red or white, are not Lua errors but rather engine errors.

Printing Your Own

If you want to print your own error messages, there are three functions to do it:

• error will print your message, halt execution, and print the stack. Normal error behavior.
• ErrorNoHalt will print the file/line number and your message without halting the script. Useful for warning messages.
• assert will check to make sure that something is true. If it’s not, it will print your message and halt just like error does.

Common Errors

Description: You tried to call a function that doesn’t exist.

Possible causes:

• Your function might be defined in another Lua state. (e.g Calling a function on the client that only exists on the * server.)
• You’re using a metafunction on the wrong kind of object. (e.g. Calling :SteamID() on a Vector)
• The function you’re calling has an error in it which means it is not defined.
• You’ve misspelled the name of the function.

Ways to fix:

• Make sure the function exists
• Make sure your function is defined in the correct realm
• Check your function calls for spelling errors

Attempt to perform arithmetic on global ‘?’ (a nil value)

Description: You tried to perform arithmetic (+, -, *, /) on a global variable that is not defined.

Possible causes:

• You tried to use a local variable that was defined later in the code
• You’ve misspelled the name of the global variable

Ways to fix:

• Make sure you define local variables before calling them in the code
• Check for spelling errors

Attempt to perform arithmetic on ‘?’ (a type value)

Description: You tried to perform arithmetic (+, -, *, /) on a variable that cannot perform arithmetic. (e.g. 2 + «some string»)

Attempt to index global ‘varname’ (a nil value)

Description: You tried to index an undefined variable (e.g. print( variable.index ) where variable is undefined)

Possible causes:

• The variable is defined in a different realm
• The variable is local and defined later in the code
• You’ve misspelled the name of the variable

Ways to fix:

• Make sure the variable is only accessed in the realm it was defined in
• If the variable is local, define it before accessing it

Malformed number near ‘number’

Description: There is a malformed number in the code (e.g. 1.2.3, 2f)

Possible causes:

• An IP address was written as a number instead of a string
• Incorrect writing of multiplication of a number and a variable
• Trying to concatenate a number to a string without a space between the number and the operator.

Ways to fix:

• Store IP addresses as a string
• Multiply variables with numbers by using the ***** operator
• Put a space between the concat (..) operator and the number.

Unexpected symbol near ‘symbol’

Description: You typed a symbol in the code that Lua didn’t know how to interpret.

Possible causes:

• Incorrect syntax (e.g. Forgot to write «then» after an if statement)
• Not closing brackets and parentheses at the correct locations

Ways to fix:

• Make sure there are no mistypes in the code
• Close brackets and parentheses correctly (See: Code Indentation)

‘symbol1’ expected near ‘symbol2’

Description: Lua expected symbol1 instead of symbol2.
When ‘symbol2’ is <eof>, Lua expected a symbol before the end of the file

Possible causes:

• Not closing all brackets, parentheses or functions before the end of the file
• Having too many end statements
• Wrong operator calling (e.g. «==» instead of «=»)
• Missing comma after table item.

Ways to fix:

• Close brackets and parentheses correctly (See: Code Indentation)
• Use the correct operators
• Add a comma after a table item

Couldn’t include file ‘file’ — File not found (<nowhere>)

Description: The file system tried to include a file that either doesn’t exist or was added while the server was live.
This error can also be a AddCSLuaFile error.

Possible causes:

• Attempting to include / AddCSLuaFile a file that doesn’t exist or is empty
• Creating a file while the server is still live

Ways to fix:

• Add the non-existent file, make sure the file isn’t empty
• Restart the server

Главная » Основные форумы » Программирование на языке Lua

Страницы:
1

Страницы:
1

Читают тему (гостей: 1)

bLib = {}
bLib['mimgui'],     imgui         = pcall(require, 'mimgui')
bLib['ffi'],         ffi         = pcall(require, 'ffi')
bLib['inicfg'],     inicfg         = pcall(require, 'inicfg')
bLib['encoding'],     encoding     = pcall(require, 'encoding')
bLib['fAwesome5'],     fa             = pcall(require, 'fAwesome5')
bLib['Events'],        sampev         = pcall(require, 'samp.events')
bLib['requests'],    requests     = pcall(require, 'requests')
bLib['Matrix3X3'],    Matrix3X3     = pcall(require, 'matrix3x3')
bLib['Vector3D'],    Vector3D     = pcall(require, 'vector3d')
bLib['effil'],        effil         = pcall(require, 'effil')
bLib['Memory'],        memory         = pcall(require, 'memory')
bLib['bit'],        bit         = pcall(require, 'bit')
bLib['Copas'],        copas         = pcall(require, 'copas')
bLib['Http'],        http         = pcall(require, 'copas.http')

for lib, bool in pairs(bLib) do
    if not bool then
        ShowPlayerMessage('Библиотека ' .. lib .. ' не найдена. Запуск скрипта остановлен!', 0x2DF61C)
        break
    end
end

function ShowPlayerMessage(message, color)
    sampAddChatMessage("[CheatHelper] {FFFFFF}" .. message, color or 0x2DF61C)
end

Description: an invalid character is placed next to a value/keyword/variable/function call

Description: indexing via [key] or .key for a variable that doesn’t exist

Description: performing arithmetic (*, /, -, +, %, ^) on a nil value

Description: performing arithmetic (*, /, -, +, %, ^) on a nil value

print(x < y) — y is not defined

Description: the number has an invalid character next to it

print(12345aaa) — aaa makes it a malformed number

Description: the pattern is missing a closing ), or a closing ]

When you get an error, Lua provides a stack trace showing you where it originates from, where the error occurs, the function calls that led to the error, and the line number of where it occurred.

The code that resulted in this error is:

First, function a is called at line 12, then function b is called at line 9 inside of a, then c is called at line 7 inside of function b, and finally at line 5, the error occurs inside of function c.

A note to add is that comments can offset the line number and make it appear as the error is in a line that doesn’t exist or doesn’t look like an error,