So do I
36 karma · joined June 9, 2014
Due to the criticism that I came across over the past few years it's unlikely I would use it for a new project though.
a guy I knew who also did alot of duping in the early days of the game once told me that he had so many items in his "depot" (kind of a bank where you could store stuff savely) that loading his depot content into memory froze the game for seconds when he opened his bank inventory.
in the early days my internet was very unreliable, that meant a disconnect during hunting meant you got killed and loose not only 10% of your progress (thats easily 10s, 100s, ... of hours of work) but also loosing all your equipment. afterwards you had to rush to the spot where you died and hope you were the first to pick everything up. without your top equipment on you it happened more than once that I died again, losing another 10% of all your skill points.
learning to deal with frustration and anger on that level was an experience that was as painful as it was life-enhancing.
This MMORPG was a university project of 4 german students from Regensburg. running on university hardware. Once they finished their studies they had to make a decision to start a company or shut the game down for good. The server was offline for days, if not weeks and the community was anxious about the outcome.
it was such a fun game to play at the beginning because everything was new. for players AND for the guys developing it. you could attack others by aiming with your mouse. so you could attack characters on your screen. but there was no range check, so you could also attack players all the way on the other side of the world if you tweaked the code. also, no cooldown, and no penalty if you aimed at a tile where no player was standing. that means you could have sent an attack command for every single tile on the game world and instantly kill every player/monster around.
Duplicating stuff was possible because the map (including all items lieing around) was saved once at 9:00am ... but your characters inventory was saved whenever you logged off. so before 9:00am you put your amazing and expensive sword on the ground, after the save you pick it up again and log out. now you wait for a server crash, which happened regularly in the early days. (and some might have figured out a way to crash it on purpose) .. after a crash a backup of the map was restored. so you could log in. your sword was on your character but it was also on the ground where you put it at map save time.
me and 3 other people organized a meetup in austria, back around the year 2000 i think. people from all over europe attended. so did the 4 german guys who created the game. out of gratitude for organizing the event we could ask for a special favour. i got a unique weapon, i think one of us got a custom house on Fibula (a tiny island south of thais) ... sidenote: most names from the beginning were latin words stemming from medicine. (Fibula: shinbone, ...)
fun times, also addictive like hell.
apt install speedtest-cli
Description: Command line interface for testing internet bandwidth using speedtest.net Speedtest.net is a webservice that allows you to test your broadband connection by downloading a file from one of many Speedtest.net servers from around the world. . This utility allows you to use the Speedtest.net service from the command line. . Note: This tool accesses speedtest.net over http, while the web-based client uses websockets. This tool has shown to become increasingly inacurate with high-speed connections. For more information, see the readme on: https://github.com/sivel/speedtest-cli
We needed something to:
- create tests without programming skills
- execute tests
- display test results
I did some basic research if there is an existing solution for our problem but haven't found something.
Recently I was given green light for publishing the code on github. To make getting started easier it's now dockerized so you can get it up and running easily.
Feedback welcome!
- ask in irc.perl.org. it is very likely to get pointers from very experienced people.
- use metacpan.org and pay attention to the votes/likes it got. and read the reviews.
- each and every CPAN module is automatically tested. look at the stats to weed out problematic modules.
- check out the release frequency and when the last release occurred.
- read the Changes file
- take a look at the tests for the module, is it well tested? are there alot of tests?
If you are past a certain point in your life as a Perl programmer this comes very natural and does not take alot of time.