Jump to content

kyeme

High Council
  • Content Count

    500
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by kyeme


  1. haha, Im also the gm cant warp. need to wait for 5 minute. T_T

    i want to be use on my player only. how to adjust ?

    Here

     

    -	script	atcmd_warpdelay	-1,{OnInit:	bindatcmd "warp",strnpcinfo(3)+"::OnAtcommand",0,99;	end;OnAtcommand:	set .@min,5;	//delay in mins	set .@gmlvl,99;	// GM lvl to bypass the delay	set .@delay,.@min * 60;	if (warpdelay > gettimetick(2) && getgmlevel() < .@gmlvl) {		set .@delaytime,warpdelay - gettimetick(2);		message strcharinfo(0),"You must wait "+.@delaytime+" seconds to use this command again.";		end;	}	setarray .@param$,.@atcmd_parameters$[0],.@atcmd_parameters$[1],.@atcmd_parameters$[2];	set .@map$,implode(.@param$," ");	atcommand "@warp "+.@map$+"";	set warpdelay,gettimetick(2) + .@delay;	end;}

  2.  

     

    @kyeme

     

     

    @var -->this type of variable will  lost  when Character re-login

    Ohh thank you :D

    how to set it for group level 2 and below only

    Here:

     

    bindatcmd "warp",strnpcinfo(3)+"::OnAtcommand",2,99;

     

    99 is for Group lvl 99.. you can control the player for example: #warp kerbii prontera


  3. a script that will put a 5mins cooldown delay on commands such as @warp

     

    -	script	atcmd_warpdelay	-1,{OnInit:	bindatcmd "warp",strnpcinfo(3)+"::OnAtcommand",0,99;	end;OnAtcommand:	set .@min,5;	//delay in mins	set .@delay,.@min * 60;	if (warpdelay > gettimetick(2)) {		set .@delaytime,warpdelay - gettimetick(2);		message strcharinfo(0),"You must wait "+.@delaytime+" seconds to use this command again.";		end;	}	setarray .@param$,.@atcmd_parameters$[0],.@atcmd_parameters$[1],.@atcmd_parameters$[2];	set .@map$,implode(.@param$," ");	atcommand "@warp "+.@map$+"";	set warpdelay,gettimetick(2) + .@delay;	end;}

  4. Few bugs:

    1. When i enable a "English Translation" both with read msstringtable.txt = false translation of some strings (all of them are string+1);
    2. When you login in game then you come to char select and clicking Cancel button => Client going to crash.
    3. Force Client Send hash packet do not work with 2013-08-07 for me.

    Diffs what i am using & exe:

    Exe 2013-08-07;

    Diffs -> Recommend + Force Client hash + few other diffs.if you need more detailed info, welcome.

     

    2. I can confirm using 2013 -08-07

    3. Works mine , Im using 2013-08-07 too. (Question: Did you set the client_hash_check: on?)


  5. 1. Na confirmed ko, maaaring bug?

    2.  Punta ka sa battle.c at lagyan mo lang ng "//" ang case AS_GRIMTOOTH: after nun i-recompile mo ang iyong server.


     


    #ifndef RENEWAL_EDP
    if( sc->data[sC_EDP] ){
    switch(skill_id){
    case AS_SPLASHER:
      //case AS_GRIMTOOTH:
    case ASC_BREAKER:
    case AS_VENOMKNIFE:
    case ASC_METEORASSAULT: break;
    default:
    ATK_ADDRATE(sc->data[sC_EDP]->val3);
    }
    }

     

    3. Ang sinasabi mo ba ay hindi nakikita sa ALT + Q (status window) yung mga items na meron % attack? ... Ito ay gumagana pero hindi nga lang kita sa ALT + Q


  6.  

     

    Update:

    Added Enable Custom Shields and Force Send Client Hash patches (Would be great if someone checks this one :) - I have tagged it as Experimental for time being)

     

     

    longshen Custom Window Title had a bug well actually bug was in the core. ill be updating it soon.

    Ill check the client date you have mentioned.

     

    @Neo do you have any plans to implement the ForceClientHashPacket? :D

     

     

    @edit

    The CustomWindowTitle is not working? My ragexe is 2013-08-07

    Ill need to look into how ForceClientHashPacket  is implemented (wew that was a mouthful)

     

    looks like there was a bug with replacing dword i have fixed it now. I'll update the repo today with all the updated stuff.

     

    Thank you.
     

    Found another bug on "Allow chat flood" when I set to 255, I cant type anything.

    And "Allow space in guild name" is not working also.. 

    Im using 2013-08-07 ragexe :)

     

    Alright ill look into that :)

     

     

    >>>>>

     

    I try to use 2013.05.22 client.

    The Custom Window Title is not working.

    The Use SSO Login Packet not working.

    I can bypass it.

    was it working for you with the xdiff file? I just checked for that client date and the changes made by the patch are same as xdiff file.

     

    @neo yes sir, its work well on xdiff.

    i have try use 2013.05.22 and 2013.08.07a, i can bypass and the sso login not works.

    hmm weird can you post the patched client here. i wonder what is wrong.

     

    This is quite awesome actually Nemo (I think you're gonna be called that from now on xD). Although the interface is much more different than Wee's, it still does what it was intended to do. xD

    I welcome any suggestions for the interface :P.

     

     

     

    Awesome updates. Thank you. :)

     

    @Allow chat flood and Allow space in guild name 

    Sorry I wasn't able to tell you that its not working with Shaktos's xdiffgen. Do you have a solution for this? :D

     

    @ForceClientHash is working now :)

     

    @CustomShield I dont know why snot showing the Shield when attacking or being attacked (i already have your .lua files)..Im using 2013-08-07


  7.  

    I think its the same as partylock mapflag

     

    PartylockDescription: Disables Party modificationsFile: npc/mapflag/partylock.txtParameter: <none>usage: <map> mapflag partylock

     

    There's a difference in using partylock and the commands from Aegis. Because partylock is a combination of PREVENT_PARTY_MAKEPREVENT_PARTY_JOIN, PREVENT_PARTY_LEAVE, PREVENT_PARTY_EXPEL

    :)


  8. longshen Custom Window Title had a bug well actually bug was in the core. ill be updating it soon.

    Ill check the client date you have mentioned.

     

    @Neo do you have any plans to implement the ForceClientHashPacket? :D

     

     

    @edit

    The CustomWindowTitle is not working? My ragexe is 2013-08-07

    Ill need to look into how ForceClientHashPacket  is implemented (wew that was a mouthful)

     

    looks like there was a bug with replacing dword i have fixed it now. I'll update the repo today with all the updated stuff.

     

    Thank you.

     

    Found another bug on "Allow chat flood" when I set to 255, I cant type anything.

    And "Allow space in guild name" is not working also.. 

    Im using 2013-08-07 ragexe :)


  9. Main problem that I can remember for killmonsterall is that all the items the monsters drop will be all scattered on the map, the reason why I didn't want to use that. You can solve it by using

    cleanmap "<map name>";

    after the killmonsterall, but beware this will also clean the items other users have already dropped there.

    Im now using the command 'killmonsterall' in my server. But the monster doesn't drop an item. Is this intended? The documentation didn't mention that the command 'killmonsterall' will not make the monsters drop an item.


  10. so I will use this one

     

     

     

    atcommand "@killmonsterall gef_fild13";  

    ??

     

    sorry double post. internet is lagging 

     

     

    -	script	Map killer	-1,{OnMinute00:	if ((gettime(3)%5)==0)	killmonsterall "gef_fild13",-1; // CHANGE THE MAP NAME	end;} 

    Try -1 or 1 not sure


  11.  

    Try this:

    -	script	Map killer	-1,{OnMinute00:	if ((gettime(3)%5)==0)	atcommand "@killmonster2 gef_fild13"; // CHANGE THE MAP NAME	end;}

    The command @killmonster2 <map name> is not working..

     

    Instead of using the command @killmonster2 <map name>, use killmonsterall instead.

     

     

    *killmonsterall "<map name>"{,<type>};This command will kill all monsters on a specified map name, regardless of how they were spawned or what they are without triggering any event label attached to them, unless you specify 1 for type parameter. In this case, mob death labels will be allowed totrigger when there is no player. Any other number for this parameter won't be recognized. 
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.