Open GoogleCodeExporter opened 8 years ago
Yup. I don't have better memory location for that. It would take time with
CheatEngine and private match testing to find the correct offset.
Original comment by sph4ck....@gmail.com
on 23 Jun 2010 at 7:26
Original comment by Drewbirmingham
on 26 Jun 2010 at 7:28
It happen sometimes when you die and some of your killstreak still active
killing in the moment of death.
Original comment by dgome...@gmail.com
on 8 Jul 2010 at 1:44
Can you get banned from using CheatEngine in private matches? If not, then I
would like to try and find the off set.
Original comment by Techmant...@gmail.com
on 11 Jul 2010 at 6:50
No, not for using in private match, as far as I know, however, I have spent 4
hours on this very task, as of now, and can not find better mem offsets, that
are static. I'm working on improving the logic so that killstreak doesn't reset
every round. But you can try if you like.
Original comment by Drewbirmingham
on 11 Jul 2010 at 6:53
Ok, thanks for the info. If you're not too busy with other stuff I'd like to
join your match and help you. Or if you have any other tasks, such as updating
file versions, readmes, I'd like to help. Because I really have not that much
to do for the next month and a half.
Original comment by Techmant...@gmail.com
on 11 Jul 2010 at 6:58
[deleted comment]
Oh nice! Ill message you on steam
Original comment by Techmant...@gmail.com
on 11 Jul 2010 at 7:03
[deleted comment]
[deleted comment]
in the version of 20.06 the killstrike counter works better than the new one
Original comment by blackber...@gmail.com
on 16 Jul 2010 at 11:42
Original issue reported on code.google.com by
Drewbirmingham
on 22 Jun 2010 at 6:03