(RSRO)Would you be interested in a clientless tool?

Quote:

Originally Posted by backo Yes, that feature is easily doable. Why isn't the stalling option in ribot working?

Most probbably iBotForFun and phBot team made a deal. So riBot no more updating ( maybie after 11D update he'll update riBot ).

Clientless Stalling isn't working since Roc update.

Cause riBot no more updating, I created clientless tool. Of course it's in beta stage, cause working only ( Server Stats, Login, Select Char, Pet Spawn, Character spawn ( sometimes crashes, need to fix it ) )

Quote:

Originally Posted by zeteris Most probbably iBotForFun and phBot team made a deal. So riBot no more updating ( maybie after 11D update he'll update riBot ). Clientless Stalling isn't working since Roc update. Cause riBot no more updating, I created clientless tool. Of course it's in beta stage, cause working only ( Server Stats, Login, Select Char, Pet Spawn, Character spawn ( sometimes crashes, need to fix it ) )

you too, nice!!

Quote:

Originally Posted by markram987 you too, nice!!

What's me too ?

Quote:

Originally Posted by backo Yes, that feature is easily doable. Why isn't the stalling option in ribot working?

As already said it was not updated for ages. So you could make it asap? :D

Quote:

Originally Posted by zeteris Most probbably iBotForFun and phBot team made a deal. So riBot no more updating ( maybie after 11D update he'll update riBot ). Clientless Stalling isn't working since Roc update. Cause riBot no more updating, I created clientless tool. Of course it's in beta stage, cause working only ( Server Stats, Login, Select Char, Pet Spawn, Character spawn ( sometimes crashes, need to fix it ) )

Yeaaah right.

Here some screens:

[Only registered and activated users can see links. Click Here To Register...][Only registered and activated users can see links. Click Here To Register...]

^^ looks good

And ye i think the clientless stalling would be best, probably the only thing i'd need.

Quote:

Originally Posted by Medically Insane ^^ looks good And ye i think the clientless stalling would be best, probably the only thing i'd need.

:) I will try to add this function. But for now stucked at char spawn :D

Quote:

Originally Posted by zeteris Here some screens: [Only registered and activated users can see links. Click Here To Register...][Only registered and activated users can see links. Click Here To Register...]

cool:D.. i gonna try that if that finished

Quote:

Originally Posted by markram987 cool:D.. i gonna try that if that finished

At the moment this tool have many bugs. Especially with item mall items.

Quote:

Originally Posted by RsX3 As already said it was not updated for ages. So you could make it asap? :D

Not really. This isn't my primary project. I'm not yet sure if it's worth the time because the rsro population is very low.

@zeteris

Looks good, keep working on it.

ofc intersted

Quote:

Originally Posted by backo @zeteris Looks good, keep working on it.

:) Not going to stop. Currently stucked on char spawns.
Need to collect more packets about pets, char spawn (when job'ing).

Not much left on spawns. This tool only crashes in crowded areas. Like Hotan or Jangan. Also not all skills and items parsed, so it causes crash.

Quote:

Originally Posted by zeteris :) Not going to stop. Currently stucked on char spawns. Need to collect more packets about pets, char spawn (when job'ing). Not much left on spawns. This tool only crashes in crowded areas. Like Hotan or Jangan. Also not all skills and items parsed, so it causes crash.

Character spawn under job has no flag.
you need to insert a statement into the items loop, if the item ID equals to one of the job items, then the player is under a job status.
and of course store the result (true or fale, 1 or 0, etc) into a variable.
why storing it into a variable?
well, there's no grant name, emblem ID, union ID, guild war status, fortress war position and stall under a job status.
so you need the variable so it will skip the whole regular process,
under a job status there's only guild name length and guild name (right after the stall flag).

If you were talking about the character data spawn (for the logged character, not other characters) then nothing needs to be skipped.
you only need to check if the player is under a job status by the same way I explained above.

Good luck! :)

Quote:

Originally Posted by Oriya9 Character spawn under job has no flag. you need to insert a statement into the items loop, if the item ID equals to one of the job items, then the player is under a job status. and of course store the result (true or fale, 1 or 0, etc) into a variable. why storing it into a variable? well, there's no grant name, emblem ID, union ID, guild war status, fortress war position and stall under a job status. so you need the variable so it will skip the whole regular process, under a job status there's only guild name length and guild name (right after the stall flag). Good luck! :)

Yes I noticed that, and made stupid mistake while checking if job status true or false :)
For now just don't know how to parse data after Grant name :)
So while I don't know how to end of the packet. I made a loop which checking for one spawn end ( 0x00FF ).

Quote:

Originally Posted by zeteris Yes I noticed that, and made stupid mistake while checking if job status true or false :) For now just don't know how to parse data after Grant name :) So while I don't know how to end of the packet. I made a loop which checking for one spawn end ( 0x00FF ).

If there's a guild name, this is what comes next:
[DWord] Guild ID
[Word] Grant Name Length
[String] Grant Name
[DWord] Emblem ID
[DWord] Union ID
[DWord] Union Emblem ID
[Byte] Guild War Status
[Byte] Fortress War Position

Now, 2 bytes before the guild name length there's the stall flag (you need to store it into a variable).
if it's 4 (0x04), there's an open stall and it goes like this:
[Word] Stall Name Length
[String] Stall Name
[DWord] Stall Model (Media.pk2 model)
* if the stall flag is anything else but 4 (probably 0), there's no stall and you need to skip this.

And then the last 2 bytes are:
[Byte] Equip/Unequip Job/Cape Timer (this yellow bar, the value is between 0 to 10 {0x00 to 0x0A})
[Byte] PK Flag (1 {0x01} = CTF PK status, 2 {0x02} = PK status enabled, 255 {0xFF} = PK status disabled)