NPC store conversation context

Paulix · Feb 3, 2026

I'm trying to build and npc that you'll be able to try and buy outfits from, the problem is that the talk sequence is a bit complex. At the moment, my behavior is working as espected, but I'm facing a major problem that I've no idea on how to solve...

LUA:

    message_table = msg:explode(" ")
    msg_action = message_table[1]
    msg_outfit = (message_table[2].." "..(message_table[3] or "").." "..(message_table[4] or "")):trim()

    if msgcontains(message_table[1], "buy") then
        if outfits[msg_outfit:lower()] ~= nil then
            npcHandler:say("Do you want to buy the " .. msg_outfit .. " outfit?\n{Base} skins without outfits is 10 coins\n{first} and {second} addon is 5 coins each\n{complete} skin + addons is 20 coins.", cid)
            npcHandler.topic[cid] = 1
        else
            npcHandler:say("I could not find that outfit, sorry.", cid)
        end
    end

The msg_outfit is working when the player says for the first time, the problem is that the npc should remember this info to use it later on the same conversation. I need to store topic to control the stage, but I also need to save the selected outfit.

How can I store this kind of information into a npc dialog, that it should keep it save in between messages, that is individual by players?

leeebux · Feb 3, 2026

You need to store it, using Storage system. ask Chatgpt to explain it you.

leeebux · Feb 4, 2026

Paulix · Feb 4, 2026

leeebux said:
So i got downvoted because i dident provide you with a readable answer?

What “storage” is in TFS (conceptually)

A storage is basically:

Think of it like a tiny database row attached to each character.

Key = a number (storage ID)

Value = a number (usually -1, 0, 1, 2, etc.)

Example:

Storage 5000 = 1 

Means: this player has progressed something

Default behavior (IMPORTANT)

If a storage was never set:

player:getStorageValue(5000) == -1 

So:

-1 = not started / never touched

0+ = something has been set

This is why you’ll see == -1 checks everywhere.

Creating a storage (there is no “registration”)

You do not create storages anywhere.

There is:

no database table

no XML

no config file

You just pick a number and use it.

Best practice: reserve ranges

Common convention:

1000–1999 = small quests 2000–2999 = main quests 3000–3999 = NPC states 50000+ = systems / global logic 

Example:

local STORAGE_MAIN_QUEST = 2000 

Reading a storage

local value = player:getStorageValue(2000) 

Typical checks:

if player:getStorageValue(2000) == -1 then -- player has NOT started end if player:getStorageValue(2000) >= 1 then -- player is in progress or finished end 

Saving / setting a storage

This is where it’s “saved”.

player:setStorageValue(2000, 1) 

That’s it.

TFS automatically:

stores it in the database

loads it when the player logs in

keeps it per character

You do not manually save anything.

Typical quest progression example

local STORAGE_QUEST = 2000 if player:getStorageValue(STORAGE_QUEST) == -1 then player:sendTextMessage(MESSAGE_INFO_DESCR, "Quest started!") player:setStorageValue(STORAGE_QUEST, 1) elseif player:getStorageValue(STORAGE_QUEST) == 1 then player:sendTextMessage(MESSAGE_INFO_DESCR, "Quest completed!") player:setStorageValue(STORAGE_QUEST, 2) end 

Progression:

-1 = not started 1 = started 2 = completed 

Using storages with NPCs

Very common pattern:

if player:getStorageValue(3001) < 1 then npcHandler:say("Hello stranger.", cid) else npcHandler:say("Welcome back, hero.", cid) end 

And when the player accepts something:

player:setStorageValue(3001, 1) 

Using storages with actions / movement scripts

Action example (lever, chest, etc.)

function onUse(player, item, fromPosition, target, toPosition, isHotkey) if player:getStorageValue(4000) == -1 then player:addItem(2160, 10) player:setStorageValue(4000, 1) player:sendTextMessage(MESSAGE_INFO_DESCR, "You found a reward.") else player:sendTextMessage(MESSAGE_INFO_DESCR, "The chest is empty.") end return true end 

Common mistakes (VERY important)

Using storage

Storage 0 is risky and sometimes reserved.
Avoid it.

Reusing the same storage for multiple things

-- BAD STORAGE = 2000 

Use separate IDs:

STORAGE_QUEST = 2000 STORAGE_BOSS = 2001 STORAGE_DOOR = 2002 

Forgetting that default is

Checking:

if player:getStorageValue(id) == 0 then 

…will fail if it was never set.

GlobalStorage (difference)

Storage → per player

GlobalStorage → shared by the entire server

Game.getStorageValue(9000) Game.setStorageValue(9000, 1) 

Use GlobalStorage for:

world events

raid states

server-wide quest phases

Debugging storages

Quick debug:

player:sendTextMessage(MESSAGE_STATUS_CONSOLE_BLUE, "Storage 2000 = " .. player:getStorageValue(2000)) 

TL;DR

Storage = per-player key/value

Default value = -1

No registration needed

Saved automatically

Use ranges + constants

setStorageValue() = saving

If you want next, I can:

show real Tibia quest patterns

design a storage map for a big questline

explain storage vs globalstorage pitfalls

show how TFS 1.4+ differs

Just tell me

You know that that's not i was looking for, I would not have come to ask for something if i wanted to use storage values, clearly storage values are not the best approach for my case, I wanted to store it temporarly just while chatting, and was looking if someone else had any solution for this specific problem.

If you are really insterested to help, don't come with this disgusting chat response that you didn't even read before posting, just stay quiet like everyone else did.

leeebux · Feb 4, 2026

That you didn’t like the answer you got, even though it’s my way of helping you, shows how ungrateful you are as a person, and it disgusts me. Go away.

Ianoyo · Feb 4, 2026

Paulix said:
I'm trying to build and npc that you'll be able to try and buy outfits from, the problem is that the talk sequence is a bit complex. At the moment, my behavior is working as espected, but I'm facing a major problem that I've no idea on how to solve...

LUA:

message_table = msg:explode(" ") msg_action = message_table[1] msg_outfit = (message_table[2].." "..(message_table[3] or "").." "..(message_table[4] or "")):trim() if msgcontains(message_table[1], "buy") then if outfits[msg_outfit:lower()] ~= nil then npcHandler:say("Do you want to buy the " .. msg_outfit .. " outfit?\n{Base} skins without outfits is 10 coins\n{first} and {second} addon is 5 coins each\n{complete} skin + addons is 20 coins.", cid) npcHandler.topic[cid] = 1 else npcHandler:say("I could not find that outfit, sorry.", cid) end end

The msg_outfit is working when the player says for the first time, the problem is that the npc should remember this info to use it later on the same conversation. I need to store topic to control the stage, but I also need to save the selected outfit.

How can I store this kind of information into a npc dialog, that it should keep it save in between messages, that is individual by players?

There are multiple ways you could do this (assuming there is no npcsystem default for this). For me, I would simply create an empty table(local) near the top of your script (not inside any function), this will stay global for your NPC script only. You can then simply store any data you want using the player's GUID(cid) as the key.

LUA:

-- top of script
local data = {}

--

data[cid] = "test" -- to set...
local val = data[cid] -- to get...

(It's not vital but.... make sure you clear any data for a player that loses focuses, it will keep the table clean)

Paulix · Feb 4, 2026

Ianoyo said:
There are multiple ways you could do this (assuming there is no npcsystem default for this). For me, I would simply create an empty table(local) near the top of your script (not inside any function), this will stay global for your NPC script only. You can then simply store any data you want using the player's GUID(cid) as the key.

LUA:

-- top of script local data = {} -- data[cid] = "test" -- to set... local val = data[cid] -- to get...

(It's not vital but.... make sure you clear any data for a player that loses focuses, it will keep the table clean)

Thats probably the best way to do it, i'll mark as solved since I manage to get it working my just using tables inside topic.
I didn't know you could set any info to topic, and thats kinda the purpose of it, I'm currently using it to control the general flow and store the informations needed per player talking to the npc at the same time.

Ianoyo · Feb 4, 2026

Paulix said:
Thats probably the best way to do it, i'll mark as solved since I manage to get it working my just using tables inside topic.
I didn't know you could set any info to topic, and thats kinda the purpose of it, I'm currently using it to control the general flow and store the informations needed per player talking to the npc at the same time.

Yep, topic is just a global Lua table inside the npcsystem, and acts just the way like I described (using cid as key), but it's usually used to store the talkstate. Either way, good luck!

NPC store conversation context

Paulix

Active Member

Ianoyo

leeebux

Awsome

leeebux

Awsome

Paulix

Active Member

What “storage” is in TFS (conceptually)

Default behavior (IMPORTANT)

Creating a storage (there is no “registration”)

Best practice: reserve ranges

Reading a storage

Saving / setting a storage

Typical quest progression example

Using storages with NPCs

Using storages with actions / movement scripts

Action example (lever, chest, etc.)

Common mistakes (VERY important)

Using storage

Reusing the same storage for multiple things

Forgetting that default is

GlobalStorage (difference)

Debugging storages

TL;DR

leeebux

Awsome

Ianoyo

Well-Known Member

Paulix

Active Member

Ianoyo

Well-Known Member

NPC store conversation context

Active Member

Awsome

Awsome

Active Member

What “storage” is in TFS (conceptually)​

Default behavior (IMPORTANT)​

Creating a storage (there is no “registration”)​

Best practice: reserve ranges​

Reading a storage​

Saving / setting a storage​

Typical quest progression example​

Using storages with NPCs​

Using storages with actions / movement scripts​

Action example (lever, chest, etc.)​

Common mistakes (VERY important)​

Using storage​

Reusing the same storage for multiple things​

Forgetting that default is​

GlobalStorage (difference)​

Debugging storages​

TL;DR​

Awsome

Well-Known Member

Active Member

Well-Known Member

What “storage” is in TFS (conceptually)

Default behavior (IMPORTANT)

Creating a storage (there is no “registration”)

Best practice: reserve ranges

Reading a storage

Saving / setting a storage

Typical quest progression example

Using storages with NPCs

Using storages with actions / movement scripts

Action example (lever, chest, etc.)

Common mistakes (VERY important)

Using storage

Reusing the same storage for multiple things

Forgetting that default is

GlobalStorage (difference)

Debugging storages

TL;DR