Euphy
-
Posts
2997 -
Joined
-
Last visited
-
Days Won
74
Content Type
Profiles
Forums
Downloads
Jobs Available
Server Database
Third-Party Services
Top Guides
Store
Crowdfunding
Everything posted by Euphy
-
-
-
-
-
-
-
-
-
-
I agree, a config seems like a good idea.
-
You can just use rAthena and disable Renewal.
-
They're the same programs, just renamed.
-
It's been in our repository for almost two and a half years.
-
Nope, works fine.
-
There's currently no script command to spawn a boss monster with a tomb. (It wouldn't be a bad idea to create one, though...)
-
Something is calling the current label (callsub) or function (callfunc). Read a bit about them if you don't know what that means.
-
The basic idea is: Block equipment changing (disable_items) -- very important! Store all the equipment data you want to keep for the gear to enchant (i.e. location, item ID, cards, refines...). Find a free card slot for the enchantment. Generate a random item ID for the enchantment. Delete the old gear (delequip), then use getitem2 to create a new piece of equipment slotted with the enchantment.
-
Reached the maximum allowed number of entries
Euphy replied to Venture's question in Database Support
The limit is set so that the server doesn't waste memory (as with most of the MAX_* defines). -
It might be easier to debug if you wrote a function/label instead of copying the same code 200 times...
-
They're differences between (presumably) the source files and the modified version. If you're running Linux, you can use the 'patch' command; else there are plenty of tools available online to patch for you (try running a search online). Or you can just copy the lines manually -- lines marked with "-" are deleted, and lines with "+" are added.
-
Basic_Scripting
-
These are custom to iRO, and were removed on other servers in an update iRO didn't adopt. You can check the file history to get the older version of the script with those NPCs.
-
Are you running it outside of the instance...?
-
As Emistry wrote, if you intend these commands to be as expressive as SQL, they'll get very complicated. Then users would have to learn both SQL and your commands. And if anything, this seems like it would be even slower than direct queries...
-
- script ::atcmd_refresh -1,{ OnInit: bindatcmd "refresh",strnpcinfo(3)+"::OnAtcommand"; end; OnAtcommand: if (strcharinfo(3) == "map") atcommand "@refresh"; end; } You can easily add conditions to any atcommand via script by this method.
