Jump to content

Nagad

Members
  • Content Count

    109
  • Joined

  • Last visited

Posts posted by Nagad


  1. Can someone adapt this old source code for eAthena that implements the timestamp for chat messages (for party/guild chat)?? Would be really cool to have it for any chat (even the normal one)

     

    clif.c

     

    Party Chat:

    void clif_parse_PartyMessage(int fd, struct map_session_data *sd){    char *mes;    int len, prefixlenparty; // ++    char prefixparty[255]; // ++    time_t t = time(NULL); // ++        strftime(prefixparty, 10, "[%H:%M] ", localtime(&t)); // ++    len = RFIFOW(fd,2) - 4;    mes = (char*)RFIFOP(fd,4);    mes_len_check(mes, len, CHAT_SIZE);    if (is_charcommand(fd, sd, mes) != CharCommand_None ||        is_atcommand(fd, sd, mes) != AtCommand_None)        return;    if    (sd->sc.count && (            sd->sc.data[SC_BERSERK].timer!=-1 ||            (sd->sc.data[SC_NOCHAT].timer!=-1 && sd->sc.data[SC_NOCHAT].val1&MANNER_NOCHAT)        ))        return;    if (battle_config.min_chat_delay)    {    //[Skotlex]        if (DIFF_TICK(sd->cantalk_tick, gettick()) > 0)            return;        sd->cantalk_tick = gettick() + battle_config.min_chat_delay;    }        strcat(prefixparty,mes); //++    prefixlenparty = strlen(prefixparty)+1;// ++    party_send_message(sd, prefixparty, prefixlenparty); // ++}

     

    Guild Chat:

     

    void clif_parse_GuildMessage(int fd,struct map_session_data *sd){    char *mes;    int len, prefixlenguild; //++    char prefixguild[255]; // ++    time_t t = time(NULL); // ++        strftime(prefixguild, 10, "[%H:%M] ", localtime(&t)); //++    len = RFIFOW(fd,2) - 4;    mes = (char*)RFIFOP(fd,4);    mes_len_check(mes, len, CHAT_SIZE);    if (is_charcommand(fd, sd, mes) != CharCommand_None ||        is_atcommand(fd, sd, mes) != AtCommand_None)        return;    if (sd->sc.count && (        sd->sc.data[SC_BERSERK].timer!=-1 ||        (sd->sc.data[SC_NOCHAT].timer!=-1 && sd->sc.data[SC_NOCHAT].val1&MANNER_NOCHAT)    ))        return;    if (battle_config.min_chat_delay)    {    //[Skotlex]        if (DIFF_TICK(sd->cantalk_tick, gettick()) > 0)            return;        sd->cantalk_tick = gettick() + battle_config.min_chat_delay;    }    strcat(prefixguild,mes); //++    prefixlenguild = strlen(prefixguild)+1; // ++    guild_send_message(sd, prefixguild, prefixlenguild); //++}

     


  2.  

    Nope, i didn't think that the exp get reset every level up.

     

    But for example there is a character that is 99/69 with 0% job exp and in the database under the column job exp there is 0, so I believe is correct right?


  3. I just noticed on my database that there are characters 99/70 with low exp.

     

    How is it possible??

     

    My server has 20x rates, everything is official so you have to kill mobs to level up.

     

    So even the Ranking chart on fluxcp has wrong values and people think that are chars created by GMs, but is not true! :S

    post-9702-0-46117100-1438011132_thumb.jpg


  4. @@zackdreaver Yeah I was thinking to do exactly the same thing, I think is the best solution actually...

     

    I'm a bit reluctant to do that because in this way I can not use my users as "testers" ahahahaha because they will never notice any error message again, so they will not report possible problems/bugs that I missed during the testing phase.

     

    Anyway, I think sometimes we can not have everything we want, right? I will find a compromise between all the possible solutions proposed by you guys :)


  5. Hey Guys :)

     

    I modified the battle/booking/navigation/rec/quest buttons in magenta 1x1 pixel buttons, but now I have this problem:

     

    juGjwvl.jpg

     

    As you can see, the "Bank" button is a little bit out of position because (I guess) there are all the 1x1 pixel buttons in the middle between the option button.

     

    Any idea how to fix that??

     

    ps: I do NOT want to diff my exe (I already now how to do that but I want to keep it "pure", that's why I modified the buttons) 

×
×
  • Create New...

Important Information

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