permanent variable vs sql

Javanese

New member
Messages
46
Points
0
Hello,

I want to consult about quest npc that using permanent variables.

As we already know that using permanent variable can be very easy to use. But i create some quest template using function setd like example below

(i use pastebin since the editing box not showing any tools.)

the problem is, when if i use this code per-npc, and if i create many npc with this function, there will be many permanent variable per npc right? So i searched about too many permanent variable issues and fund annieruru explanation on eathena.

So i am planing using sql as quest database. Is there any issues if i store the quest detail on sql and all my quest npc will load from there? because i am planing to create a lots of quest with different npc.

thank you

 
If I remember well, Hercules removed all the variable limitations around a couple months ago, so you can now use all permanent account, char or server variables you like without any problem. Look for any scripting engine update on our Repository News topics.

 
btw variables are saved on SQL also
default_tongue.png


 
In fact, using variables is slightly faster than doing all the queries right away. Variables are stored in memory until the player gets saved, that is when all the information goes straight into the database. This way you save some processing time
default_tongue.png


 
Back
Top