Leaderboard

View File cp_itemdesc populed table I don't know the reason but on my Fluxcp the system "UPLOAD ITEMINFO.LUA" never worked and so I took the file "itemInfo.lua" file translated by @zackdreaver (GIT repo) with all the descriptions of the translated items formatted in HTML and I have made a SQL file that inserts the data in the `cp_itemdesc` table which should be enabled on the Fluxcp "Add Item Info" page. The option to activate the description of the items is the following in the file "/config/application.php": 'ShowItemDesc' => true, // Displays generated item descs from parsed itemInfo.lua It depends on the configuration of your "phpmyadmin" (if you use it), but it is very likely that you will need to split this SQL file into several parts to avoid timing out during the query run. if you want to thank me, you can give me a "LIKE"! ;D p.s.: the first 8 items on the list are custom of my server! Submitter CyberDevil Submitted 04/05/2018 Category Other Web/CP Scripts Video Content Author CyberDevil  

Just want to leave a (second) big thank you here. I'm using this since 2018 for singleplayer experience and LAN play with friends. This package is top notch and totally hassle free. You are doing a great job in your free time. Kind Regards

32107,Adaga_da_perdicao,Adaga_da_perdicao,4,2400,,600,43,,1,4,0x00001000,7,2,2,1,1,1,1,{ if(getequipid(EQI_HAND_R) == 12345){ unequip(EQI_HAND_R); dispbottom "You can only equip one type of this weapon."; } else if(EQI_HAND_L == 12345){ unequip(EQI_HAND_L); dispbottom "You can only equip one type of this weapon."; } },{},{}

New GM, Commands & Permissions system has been added in r15572. Unfortunately, this update is not backwards compatible with previous revisions and requires reconfiguration of existing rAthena installations. This new approach is designed for easy maintenance, increased flexibility and readability. Hopefully it will make up for migration difficulties. General description The whole concept of GMs and non-GMs as well as GM levels has been abondoned in favor of more role- and privilege-oriented player groups. Each account belongs to exactly one group. Player groups are independent of each other, so unless you decide to do so, they don't have to share any privileges like it was with top-down GM level hierarchy. There is, however, a way to say which group is higher, and which is lower: it's group level. Each group has following atributes: ID — unique number name level — it can be interpereted as (GM) level of all group members commands settings — what commands can group members use permissions settings — what other permissions group members have inherited groups — permissions and commands from which groups are inherited log commands — should commands issued by this group be logged or not Groups are configured in conf/groups.conf file. The file itself is fully documented and contains default configuration that should be adjusted to your needs. Details Column `login`.`gmlevel` has been renamed to `group_id`. It now stores ID of the group player belongs to, so you need update your database accordingly. Atcommand configuration file conf/atcommand_athena.conf no longer defines GM levels required to use the command. Permissions to use commands are now defined for each player group separately in group configuration file conf/groups.conf. Command aliases are still being defined in conf/atcommand_athena.conf. File syntax has changed. Import is no longer supported for this file. File is fully documented and contains default aliases that were present in previous revisions. GM configuration file conf/battle/gm.conf no longer defines GM levels required to get some privileges (like trading or partying). See full list of removed settings:These permissions are now defined for each player group separately in group configuration file conf/groups.conf. Player titles defined by conf/battle/gm.conf settings title_lvl1 to title_lvl8 and conf/msg_athena.conf (335~342) are replaced with group names. Removed @adjcmdlvl command. Replaced @adjgmlvl command with @adjgroup, which allows to temporarily (until relog) move player to another group. In login-server configuration file conf/login_athena.conf min_level_to_connect setting has been replaced with group_id_to_connect setting, which allows you to define account group id that is required to connect to server. In char-server configuration file conf/char_athena.conf gm_allow_level setting has been replaced with gm_allow_group setting, which allows you to define group id that is allowed to bypass the server limit of online users. In log configuration file conf/log_athena.conf log_gm setting has been replaced with log_commands setting, which allows you to decide whether commands should be logged or not. Even with command logging enabled, only commands issued by groups that have log_commands set to true will be logged. About group level Group level is used only: when determining if player can override trade restrictions defined in db/item_trade.txt when determining if player can use @command on another player (existing rule that low-level player can not use some commands, eg @kick on high-level player has been kept) or see another player with @who commands (if they have "hide_session" privilege). as a return value for getgmlevel() script command when determining if player can use commands in a map with nocommand mapflag set Other CMakeLists were not updated. If you know cmake and want to contribute, just send me (or other dev) a diff. There were multiple minor changes in this revision. For full list, see rAthena Trac (r15572) or SVN log.