87 karma · joined September 11, 2013
Being skeptical and keeping onself safe is fine, but things can go wrong if people are trying to falsely act like experts.
Low-friction interfaces for developers are great but I'm not sure I agree with the comparison here.
- https://en.wikipedia.org/wiki/Space_Launch_System - https://en.wikipedia.org/wiki/Human_mission_to_Mars#Current_...
[1] https://www.theguardian.com/technology/2014/apr/15/gmail-sca... [2] http://www.reuters.com/article/us-internet-extremism-databas...
"Figure 5 shows the peak zone memory improvements since M54 which reduced by about 40% on average over the measured websites. "
From: http://v8project.blogspot.ca/2016/10/fall-cleaning-optimizin...
[1] https://github.com/dutchcoders/transfer.sh/blob/master/trans...
[2] https://github.com/dutchcoders/transfer.sh/blob/master/trans...
There were some really interesting "innovations" in those scripts compared to the other free ones that were available at the time. For example, this script would allow the character to harvest and store wood from trees that would regrow / respawn. This script would time each hardcoded tree to count how long it had been de-spawned (dead) in order to move the bot user to wait by the tree that had been de-spawned the longest when all of the others were de-spawned. This was a good way to avoid being reported because most bots would just wait by the last tree to de-spawn and then instantly start moving to the first one that respawned.
Some other interesting tricks could be found in the "antiBan" method in a lot of scripts. Given a random input this script would move the mouse in some random ways, check some random stats, move the camera around, etc. One additional "antiBan" approach that I implemented for this script was to "take breaks". The idea was that a real player would probably not be watching their account and harvest the wood with perfect efficiency all of the time. Telling the bot to "take breaks" meant that it would turn itself off entirely for a short time (maybe a minute?) and just not react to any input, as if you were using the restroom or doing something else.
I could talk about this stuff for ages, it was great fun. :)
P.S. I have a tiny blurb about it on my website too: https://www.dwett.com/projects/#runescape-bot
The biggest problem that I ran into with this approach however was checkpointing. I could never correctly reason about a way to prune the log of updates that you apply that still allows (100% correct, intent-preserving) merges from someone that might have been offline since the dawn of time. Does anyone know if this issue with this approach was ever solved?
(https://www.dropbox.com/s/98kngmtwzrsmvjg/Screenshot%202014-...)
It's really poorly formatted and has unused code in it but it was fun to automate and watch. http://pastebin.com/yTmdWgfC
To use it just install the bookmarklet, click on it and then start the game. Press space to make it die.