AutoUpdate project

[Casky]

As I know byte is unsigned, so it's not negative, and as I said, I changed it to a int array, the 0xFFF was just to explain my idea hahahaha

[szulak]

Now my competitors know my secret to 30-minute updates, though >

Integrate this process with any CI, and you will get 5-minute update.

[DarkstaR]

Integrate this process with any CI, and you will get 5-minute update.

This method doesn't always work (assembly code can change), and it's very hard to test with CI.
e.g. how can my CI test cases known that my healer worked without relying on the fact that my health address is right, which is 50% of the healer working? Maybe I could use CV to detect the current health and health % and make sure it heals..Okay. So what about the walker, how do I verify that it is working? How smart would my CV need to be? How do my CV based test-cases deal with the fact that Tibia is stochastic, not deterministic? etc etc

Verifying updates need to be done by hand unless you really hate your customers and give 0 shits about their characters. My update system will automatically download and install new Tibia updates, then automatically run the address locator and commit the new file to a new branch, but beyond that, it needs to be manual. That's why my update system very graciously wakes up me when there is an update.

[szulak]

This method doesn't always work (assembly code can change), and it's very hard to test with CI.
e.g. how can my CI test cases known that my healer worked without relying on the fact that my health address is right, which is 50% of the healer working? Maybe I could use CV to detect the current health and health % and make sure it heals..Okay. So what about the walker, how do I verify that it is working? How smart would my CV need to be? How do my CV based test-cases deal with the fact that Tibia is stochastic, not deterministic? etc etc

Verifying updates need to be done by hand unless you really hate your customers and give 0 shits about their characters. My update system will automatically download and install new Tibia updates, then automatically run the address locator and commit the new file to a new branch, but beyond that, it needs to be manual. That's why my update system very graciously wakes up me when there is an update.

You're most likely right. However, this process can be improved a lot - I don't know how does your design and implementation of your bot's internals looks like - but the proper design would allow (or should allow) very high test coverage - which can be run by CI. Assuming your design is pretty flexible and you have very high test coverage, upon new client version CI could perform an auto-update, run unit tests and then - the hard bit comes. But firstly, I would wonder what tests you're performing in this moment to say "it works" - and wonder, if this can be automated - pretty sure, it could (by faking game server etc etc).

[Blequi]

My update system will automatically download and install new Tibia updates, then automatically run the address locator

That's a really cool idea.

After running the address locator, if the tool was able to find most of the key structures, a message could be sent to users like "keep calm, because our automated process was able to update critical structures"

[DarkstaR]

and wonder, if this can be automated - pretty sure, it could (by faking game server etc etc).

But if Tibia changes their protocol (not too rare), your tests break. I'm all for CI, and I use it in my day job and love how powerful it is.. but most CI isn't testing very specific interactions with stochastic closed-source systems.

That's a really cool idea.

After running the address locator, if the tool was able to find most of the key structures, a message could be sent to users like "keep calm, because our automated process was able to update critical structures"

I'm normally done updating by the time anyone notices, and XenoBot pulls the updates in the background. Many of my users don't even realize when updates happen, nowadays

[klusbert]

https://github.com/klusbert/MemoryScanner