Expire: %s (RentItems)

[herenow]

Hello. First of all thank you for you attention.

Well... For the past hour i have been trying to figure out how to fix the Expire: %s problem..

What happens is that when i rent a item. Its descriptions should show when the item will expire. Example: Expire: 02/12/05:13

But insted it shows Expire: %s. So maybe the source isnt sending the information to fill in the %s? Or maybe the client im using 2010-07-30 does not have this feature?

Does anyone know if this is a source problem? or if it can only be fixed changing the client? I dont really think its src related. And im having a hard time to get my 2011-06-09 to work on the eamod. I dont really know why. It passes the login-server but when its trying to connect to the char-server it gets timed outed (cannot connect...). And im so sleepy that i cant really think straight rs. So here i am. Asking for help.

Thanks.

Edited February 12, 2012 by herenow

[JayPee]

I think this is a reference for that: http://www.delorie.com/gnu/docs/glibc/libc_437.html

[herenow]

I think this is a reference for that: http://www.delorie.c...c/libc_437.html

Well you are saying its a problem at the source then? Well just woke up ill give it a better look today.

@edit

Well after some tests.. Its not a data problem.. Not a source problem.. Its the 2010-07-30 client problem. Anyone knows a fix?

Edited February 12, 2012 by Tribbiani

[Dia]

What's your clienttype in xml? I had the problem when I had germany in it.

[Gepard]

I'm quite sure it's a bug specific to 20100730 client. I could be fixed by hex editing probably, but I recommend choosing another Ragexe, that is not bugged.

[ngek202]

tested on 20100730 seems to be working fine.

[Gepard]

Can you post the line from msgstringtable.txt, you're using?

[ngek202]

here it is.

msgstringtable.txt

[Gepard]

Oh, it works for me too, all of the sudden. In case it matters, servicetype is america, langtype 0, version 25

[herenow]

Well i use 2010-07-30aRagexeRE

Well i im pretty sure i need to change the hexed. I did try to edit he HEX but then i figured out i didnt really know what I was doing.

Does anyone know a hex fix for this? Well im gonna try some other hexed in the mean while.

@gepard

What did you do to fix it? Changed the clientinfo?

@edit

Well issue is kinda resolved. I am developing a server with a friend and i was using his 20100730. I diffed one just like ngek202 (kro) and it worked. I dont really know where the hell did he get this hexed.

Thanks for the help.

Edited February 12, 2012 by Tribbiani