New Feature: User Paging

Hey guys!

I've just added a new feature to Chronos, which is the ability to "page" your users!

Basically, admins can now select a user from the connected user list on their overview and click the "Page User" button. This will then cause the user to be notified that their attention is required. This is useful for calling in raiders who are sitting out, etc.

Client users can set up what sound to use for their page in their Basic Settings. This box works the same way as setting up text to speech / sounds in timers and triggers. Simply type something you want it to say upon receiving a page, or look for a WAV file to play instead.

Users that have received a page will get a flashing notification at the bottom of Chronos and their chosen sound effect will play once every 3 seconds. They can stop their "page alarm" by clicking the "End Page" button in the bottom right of the program. Of course, you can only see this button if you are currently being paged.

Admins that send a page to a user will receive an automatic notification in their log box that the user has successfully been paged. This message is a definite confirmation receipt, so there's no "I didn't get it!" excuses! The admin will also receive a notification in their log box when a user ends their page alarm in their client. This is useful for knowing when someone has seen the notification and have responded to it. There's a new option in the Basic Settings of the admin version that will allow you to turn on or off an audible speech notification that a particular user has turned off their page alarm.

Have fun!

Larks.

Quick Update

I've added in an "Inherit Style" checkbox in the themes panel. If this is checked, it will inherit the styling from the theme you're activating. If it is unchecked, whenever you activate a theme it will keep your current color settings in the new theme.

Happy theming!

Version 0.4.3.0 Released! Overlay theming introduced!

Hey everyone!

Chronos has been updated and now supports overlay themes!

You can create themes by editing a .chronosoverlay file. These files can be found in your ChronosServer or ChronosClient folder under OverlayThemes. Simply copy the default theme (1.chronosoverlay) to your desktop (don't make a copy in the same folder) and then edit it as you like! Next, head to the basic settings page of Chronos and add your new theme!

When you first start Chronos, your current overlay settings are preserved.

However, activating a theme (whether or not it is already active) will inherit the theme colors. You may put your own colors on top after that point by changing the usual overlay settings, but remember that activating a theme again will use the colors from that theme again.

So basically, load a theme up and change the colors how you want :).

I've started the ball rolling with a "compact" theme available on the downloads page. Be sure to let me know if you guys come up with any interesting themes!

By the way, if you need to change the colors of the timer progress bars in any custom themes you might create, you'll need to set Overwrite Windows Style to [True]. If you've loaded Chronos with the default green Windows progress bars and you've tried to change their color, try applying your theme and restarting Chronos to make it show up correctly.


Thanks!


Feina.

0.4.2.0 Released

Just a few updates today!

Chronos now saves the text in your logbox to dated logfiles in either your ChronosServer or ChronosClient folder. I will probably be adding in extra "detail" output information to these logfiles later.

I've also added in a bunch more "Chronos tags" that you can use in your HTML code to display extra data on your web report page (sample), along with the option to automatically update this page whenever you start or stop your server or close Chronos.

Thanks!

Larks.

Chronos 0.4.0 Released!

Hey everyone!

Chronos 0.4.0 has been released, which includes an updater! I've ironed out a few bugs, including a bug which prevented personal events having timers longer than 100 seconds (thanks to Anonymous for the report).
The file structure of Chronos has also been significantly changed, so this means that you can not simply update your executable with this version. Don't worry, I don't expect to make file structure changes ever again. Hopefully, for the first and last time, here are the steps on how to update and keep your current data:

1) Go to your current Chronos directory.
2) Back up your entire Chronos directory to a different location.
3) Download a fresh install of Chronos from the Downloads page (the full RAR)
4) Extract the files back to your original Chronos directory, or to wherever you like
5) Run the fresh install of Chronos and then close it
6) Go to your backup of Chronos and copy all of your .chronos files
7) Go back to your fresh install of Chronos and paste all of your .chronos files into the ChronosServer or ChronosClient folder (depending on your version)
8) Open Chronos, go to your update settings on the Basic Settings page and change your update URL to http://chronostimers.info/Chronos/

That should be it!

If you're wondering, the Icons folder can now be found in the ChronosData folder.

New users of Chronos can simply download the full installation and follow the instructions on the Downloads page as normal.

As always, please report any bugs with the updater or Chronos itself either by commenting on the blog or Emailing chronosdevelopment@gmail.com!

Thanks,

Larks.

Version 0.4.0 Incoming

Downloads have been taken offline while I make the necessary changes to the downloads page.

Thanks.

Multiple Log Files

I've wrote the code to allow the use of multiple log files in Chronos. I'll be implementing it all into the existing program tomorrow and releasing a new build (providing all goes smoothly).

This means that if your game splits up log files into different files (for example combat and chat like Rift), or if you want to keep multiple log files active (for example if your game uses different logs for different characters like EQ2), you'll be able to do this.

The amount of log files you can have "active" at once is unlimited, but the files are at least accessed every log read interval (default of which is 10ms), so having a lot of log files may impact performance even if they're not being written to by your game. As far as I'm aware, you'd need a lot of active logs to even notice a difference.

The only thing I should add is that if you have multiple logs that are under actual heavy access from your game(s), the software will need to pull data from each one every log read interval, so if there's lots of data pouring into lots of logs, it's going to slow down the reaction times of the software as it loads big chunks of data to work on at once. Just something to keep an eye on.

However, if you have something like 2 or 3 active logs being written to at a time, which is the most likely scenario, it shouldn't cause an issue whatsoever.

Logfiles that get smaller (for example, if your game clears the logfile or archives its contents) and logfiles that disappear (for example, if your game removes your log file when you exit) shouldn't cause any issues and are taken care of as part of the code. Log files that no longer exist (like disappearing ones) will stay in your log list, but wont be accessed again until they do exist.

Testers

Hey guys.

I see from my traffic that Chronos has already been linked on several guild forums etc (which is awesome, thanks!). At the moment I'm not tracking downloads, so if it wouldn't be too much bother could anyone trying out Chronos drop me a comment on the blog with what version they're testing and any initial comments.

You can also send me an Email at chronosdevelopment@gmail.com.

I'd like to have an idea of the level of interest, but I'd rather not have to spend time writing a download tracker script if I can help it :).

Don't be shy about mentioning features you'd like in the software, although keep in mind that I will not be implementing a dps tracker. There are plenty of excellent parsers already, like ACT, that don't need reinventing.

Thanks.

EDIT: Comments can now be made by anyone (they will appear after moderation).