Search results
-
bad argument #1 to 'find' string expected, got nill
no the message is literally nil it says argument #1 in the error message to string.find don't know what else to tell you because i don't know what that message is supposed to say or what that npc is or where its from -
bad argument #1 to 'find' string expected, got nill
read the error it says its in string.find in the code you posted and you even commented the lines -
bad argument #1 to 'find' string expected, got nill
the greet/goodbye messages if u read the error are nil -
addskill for levels does not work above 71k levels tfs 1.3
u need to change int LuaScriptInterface::luaPlayerAddExperience(lua_State* L) change experience from int64_t to uint64_t, result: uint64_t experience = getNumber<uint64_t>(L, 2); and u can add a bit of extra xp (i add 10k) when it calculates 0 because the calculation isnt precise so its sort of... -
-
TFS 1.X+ 8.60 Downgrade by Nekiro crashing
recompile with cmake -DCMAKE_BUILD_TYPE=Debug .. then run bt full so we can actually get info about the crash -
Lua Xikini's Free Scripting Service TFS 1.3
u dont need a script buddy its literally in items.xml criticalhitchance and criticalhitamount -
Lua Xikini's Free Scripting Service TFS 1.3
....but theres crits in 1.3 already lol? -
Updrage system
the problem is if you do it separate and try to use old items.xml absorb/protect value + new one, when using onStatsChange you get the value AFTER the original absorb is calculated, so then you're going to reduce it even more because there's no way to add both of them together before calculation... -
Updrage system
hidden from desc and separate from the actual ability/attribute in items.xml where u cant stack the 2 yes sure -
Updrage system
protection isn't an attribute, theres no way to do it like an attribute and use this same script without a source edit -
C++ Doubts About C++ Source TFS 1.3
figured i'd add some extra information so you properly understand how a C function works, so here we go: it's important to fully understand how a stack works and what's being added / removed when using the lua C api as well as you'll notice almost all functions return 1 in luascript.cpp, just... -
Does not add item to player TFS 1.3
it will be missing but we dont know if his server has promotions or if he only has 4 base vocations overall, i just took the ids he used himself -
Does not add item to player TFS 1.3
pls dont write it like that local rewards = { [1] = 7958, [2] = 2184, [3] = 7438, [4] = 2451 } function onUse(player, item, fromPosition, target, toPosition, isHotkey) if player:getStorageValue(52003) == -1 then local reward = rewards[player:getVocation():getId()]... -
Teleport does not disappear ( tfs 1.3 )
change addEvent(removeTeleport, 1 * 60 * 1000, position) to addEvent(removeTeleport, 1 * 60 * 1000, teleportCreatePosition) -
TFS 0.X show list of players with same storage
can actually also keep track of index manually to make it even faster instead of using # operator each time function onUse(cid, item, fromPosition, itemEx, toPosition) local onlinePlayers = getPlayersOnline() local players = {} local index = 0 for i = 1, #onlinePlayers do... -
TFS 0.X show list of players with same storage
and t[#t+1] = val is faster than table.insert -
C++ Doubts About C++ Source TFS 1.3
lua_State* L is a pointer to the information in the lua state you use it to access information inside of the state via the lua C api when you send arguments through lua to a function such as Player.sendTextMessage, they are added to the stack in your example, this is how the stack looks like... -
-
Do you want to make money during quarantine?
he starts responding to shit after nobody has said anything in 3.5 months mental breakdown i guess- Infernum
- Post #16
- Forum: Discussion