Maki Posted September 5, 2012 Posted September 5, 2012 @warp_Modification I suggest that this should be default for rAthena; do not understand why it isn't as almost all servers use this (and if they don't, no loss to them).
Joseph Posted September 5, 2012 Posted September 5, 2012 I don't see any reason for not adding this. +1
Sneaky Posted September 5, 2012 Posted September 5, 2012 Indeed most servers use this function, but there are also servers that they don't (They like it better to just Resurrect via warp), I'd say make it a conf that applies for both at go and warp, in /battle/misc.conf. warpbeingdead: yes/no Or, just let 'em add/remove the code however they want it to work. But yeah as I said above at least the mayority of the servers use that function. 1
Euphy Posted September 5, 2012 Posted September 5, 2012 Agree with Spyra, but I think the conf should disable all atcommands when dead (except ressurection commands, of course). 2
Brian Posted September 6, 2012 Posted September 6, 2012 Some (probably high rate) servers allow @go/@warp/@load when dead so players can hotkey an @command and be lazy and not have to click "Return to Save Point". Which majority do we cater to? Also, server owners might want to allow GMs to use @commands while dead. Adding to the above suggestions, how about we add a permission to trunk/conf/groups.conf to allow that group to use commands while dead. Maybe call it 'commands_while_dead' or 'use_commands_while_dead'. 4
Kenpachi Posted September 6, 2012 Posted September 6, 2012 I think it should be a conf which by default allows to use @commands when dead. (Î never tried it but on official servers GMs probably are allowed to use commands when dead.)
Ind Posted September 6, 2012 Posted September 6, 2012 Oki, group setting then. Added in r16751 as discussed 1
Euphy Posted September 6, 2012 Posted September 6, 2012 How about @alive/@raise/@raisemap exceptions? (might not be needed, but just throwing the idea out there)
Recommended Posts