tr-jobs answers questions through jo_libs callbacks. Call them with jo.callback.triggerServer, either with a function that receives the answer later, or without one to wait for the answer.
Calling from the server
From a client, the server knows who's asking. From the server, there's no player behind the request, so pass the player's ID yourself, as the first value. If you leave it out, the next value you pass (a job name, say) is taken as the player.
tr-jobs:getCurrentJob¶
The player's current job and grade.
-- client
local job, grade = jo.callback.triggerServer("tr-jobs:getCurrentJob")
jo.callback.triggerServer("tr-jobs:getCurrentJob", function(job, grade)
-- ...
end)
-- server
local job, grade = jo.callback.triggerServer("tr-jobs:getCurrentJob", source)
jo.callback.triggerServer("tr-jobs:getCurrentJob", function(job, grade)
-- ...
end, source)
tr-jobs:getMyJobs¶
All of the player's job assignments, as a table (the same as getjobs).
-- client
local assignments = jo.callback.triggerServer("tr-jobs:getMyJobs")
-- server
local assignments = jo.callback.triggerServer("tr-jobs:getMyJobs", source)
tr-jobs:getPlayersWithJob¶
Every player with a job at a grade.
-- client
local players = jo.callback.triggerServer(
"tr-jobs:getPlayersWithJob", job, grade)
-- server (0 stands in for the player asking)
local players = jo.callback.triggerServer(
"tr-jobs:getPlayersWithJob", 0, job, grade)
tr-jobs:getJobFamily¶
The family of the player's current job.
-- client
local family = jo.callback.triggerServer("tr-jobs:getJobFamily")
-- server
local family = jo.callback.triggerServer("tr-jobs:getJobFamily", source)