Read & accept THIS before downloading

Read & accept THIS before using / downloading Chronos

Thanks for your interest in Chronos!

Before you download and try out the program, there are a few things you need to know and accept. If you don't accept these things, then you do not have permission to use Chronos.

First of all, Chronos has been coded with absolutely no intentional malicious code whatsoever. It is not designed to cause damage to your machine, steal data, give you advertising or anything else you wouldn't expect from this kind of software.

However, because Chronos is a prototype and very much a learning experience for myself, there may be unexpected things that happen. Some of these things may include program and / or system crashes. Obviously throughout coding Chronos, I have had program crashes, that is pretty much a given with any software at any stage of development or release. I have not, however, had any major system crashes (blue screens, etc) but they are entirely possible, just like with any other software.

Knowing that Chronos is a prototype and I'm absolutely no expert C# .Net programmer, you accept that I waiver all responsibility for the use of Chronos, although I do retain copyright. You use it entirely at your own risk and you accept that the program may or may not be riddled with bugs, errors, security holes, etc. You also accept that you are aware that Chronos does not use encryption of any kind (except for when your username and password are sent to the server) and does not use SSL. Most, if not all data is sent and stored as plain text (although I expect to implement encryption in later versions). Keep in mind that when Chronos communicates with a server or client, it does NOT send your entire log. In fact, it sends the minimal amount of data needed to work. For example, triggering an event would send the event ID, any extract, username (if you've inserted a username replacement ^) and that's about it. You also accept that Chronos accesses your hard drive to read designated log files at an extremely frequent rate and currently does not "sleep" while the logs are inactive.

I try my best with the time that I have to make Chronos reliable and useful, as I use it too. It helps me if you report any issues back to me at my development Email address, which is chronosdevelopment@gmail.com. One of the planned stages of Chronos before entering beta is a complete code rewrite with all of the knowledge and experience I have gained coding the alpha / prototype.

You also accept that you will not misuse Chronos for any malicious intent (regardless if a program bug or "feature" appears to allow this), including but not limited to harassing, stealing data and causing crashes or unwanted effects to anyone or anything. You also agree that if you discover any security holes, bugs, exploits, strange or unexpected program behaviour or anything similar or related, you will report them immediately, in full, with as much detail as you can possibly provide, to myself via the development Email address ( chronosdevelopment@gmail.com ).

You accept that you should scan all downloads for viruses / spyware / malware etc and be satisfied that it is free of anything potentially related. Even though I didn't program Chronos to be intentionally harmful, anything can happen between me uploading it to a server and you downloading it and I take no responsibility for infections or malicious software. It's always safe to check!

You agree that I reserve the right to make changes to or make unavailable any part of Chronos for download and / or use and you also agree that I reserve the right to push updates or modify your Chronos files via the updater.

Finally, you also accept not to attempt to decompile the software or edit the source code, and you should not imitate Chronos maliciously. Please refrain from distributing or reselling the software to other people, but instead direct them here so that they can also read this message and download / obtain it from me only. It's only fair that they know exactly what they're using.

If you don't agree to any of this, simply don't download or use Chronos, but I hope you'll still follow the development until you do feel comfortable using or testing the software.

Right now, I'm looking for people to test and use Chronos in every day situations (raids, groups, etc). Although I wouldn't actually say the program is ready for every day use, there's really only so much I can do keeping it "in house", which is why this blog has been created; to distribute builds to the community so that they can help me develop and improve the software to suit the needs of everyone.

If you do have any blue screens, it's very important to let me know what you think was happening right before it happened. Were a lot of people logging in or logging out? Were you editing a user or something similar? These things help me improve the thread safety of Chronos and avoid major crashes.

Any minor errors should be reported in as much detail as possible. Was there any error text? If so, what was it? What were you doing at the time? Can it be reproduced? Make sure you copy the full error report if there is one, take a screenshot and shoot it over to me via the development Email.

I also reserve the right to adjust these conditions at any time and it is your responsibility to stay up to date with the contents of this agreement, as per your continued use of any version of Chronos.

If you like, you're welcome to simply use Chronos as it is without leaving general feedback. However, everything above still applies.

Thanks for reading, have fun playing!

Click here to go to the Chronos download page.