Jump to content
For maintenance and updates, the community will be offline on 31 December 2022 ×
  • 0

Questlib mysql_query function problem



Hello, i have one query in quest like (ex.):

local test= mysql_query("SELECT * FROM player.my_system WHERE player_id = '"..pc.get_player_id().."' AND time >= '"..max_time.."' LIMIT 1")
if test == 0 then



but in syserr i have all time:

RunState: LUA_ERROR: locale/turkey/quest/questlib.lua:33: attempt to call global `split' (a nil value)

33 line in function mysql_query is: for av in io.open(fi,'r'):lines() do table.insert(t,split(av,'\t')) end; os.remove(fi);

screenshot: https://metin2.download/picture/wl9K9DEs2LoeO9WwbhiCLPzHuevut8ge/.png

and in channel directory have much files mysql_data_***, which generate from mysql_query function:  local fi,t,out = 'mysql_data_'..math.random(10^9)+math.random(2^4,2^10),{},{}

how can fix it?

Edited by Metin2 Dev
Core X - External 2 Internal
Link to comment
Share on other sites

2 answers to this question

Recommended Posts

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Activity

    1. 993

      [40250] Reference Serverfile + Client + Src [15 Available Languages]

    2. 1

      Looking for a good designer

    3. 0

      Cross channel friend request

    4. 2

      Where are those maps/dungeons coming from?

    5. 3

      Press F10 to close the client immediately

    6. 2

      Where are those maps/dungeons coming from?

    7. 2

      Where are those maps/dungeons coming from?

    8. 4

      Visual studio 2022 compiling issue

    9. 1

      Count players function

  • Recently Browsing

    • No registered users viewing this page.
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.