Jump to content
adc

Help me find a pattern to this madness

Recommended Posts

I've been trying to obtain the barrows killcount via the config debugger. It appears that config #453 is the correct place to look, as it changes consistently every time killcount changes, and when killcount reverts to 0, config(453) also reverts to 0. However, the numbers that it returns have no apparent pattern. I've recorded (most of) the values from 4 barrows runs :

0 --------- 0 --------- 0 --------- 0
138436 ---- 138434 ---- 138434 ---- 138464
275788 ---- ?? -------- 275779 ---- 276912
414236 ---- 414227 ---- 413131 ---- 414264
552700 ---- 552691 ---- 551579 ---- 551609
690045 ---- 691127 ---- 690043 ---- 690043
828479 ---- 827127 ---- 828479 ---- 826043
964479 ---- ?? -------- 962879 ---- 959867
1100479 --- 1097527 --- 1096703 --- 1093691
1234879 --- 1233527 --- 1232831 --- 1232127
1370879 --- 1367927 --- 1368831 --- 1368127
1505855 --- 1501751 --- 1502655 --- 1504127
1636927 --- 1636919 --- 1636927 --- 1636927
1767999 --- 1767991 --- 1767999 --- 1767999
1899071 --- 1899063 --- 1899071 --- 1899071
1964607 --- ?? -------- 1964607 --- 2030143
2095679 --- 2095679 --- 2095679 --- 2095679 

Line number indicates Kill Count value, and ?? indicates that I wasn't able to get the info (other cofig data push it out of view too quickly).

 

 

Any ideas as to what the pattern might be here? (Or am I unaware of something crucial regarding jagex's config files?)

 

Edited by adc
Link to comment
Share on other sites

Can't find anything but can't you just count the number of monsters killed? not that it's like multi

 

 

I could, but in the case that for some reason the person's kc is not 0 when they start a run, it'll throw everything off. This could happen if they partially complete a run, stop and restart the script, pause it to do something else and accidentally get more kc, etc. While I could keep persistent variables, it still wouldn't allow me to account for all scenarios :(

Link to comment
Share on other sites

I could, but in the case that for some reason the person's kc is not 0 when they start a run, it'll throw everything off. This could happen if they partially complete a run, stop and restart the script, pause it to do something else and accidentally get more kc, etc. While I could keep persistent variables, it still wouldn't allow me to account for all scenarios sad.png

Incase you didn't figure it out, use:

 

killCount = config >> 17;

  • Like 1
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.


  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...