For the past half year myself and other developers have been building a service that provides game analytics called Lumos. With Lumos you can track things like runtime errors, player engagement (monthly active users, new registrations, etc.), and the system specs of your players. We also built an integrated feedback system that allows you to easily gather bug reports and suggestions from players.
We’re just launching, and we’d love to hear your feedback. The system has been built to run as automatically as possible – you don’t need to do any coding to take advantage of the features, and it’s free to use (there’ll be a paid option eventually, but we’ll always offer a basic package for free). The website is www.uselumos.com. We don’t yet have the unitypackage available on the Asset Store, though that will hopefully be uploaded soon.
Let me know if you have any questions or suggestions. We’re actively developing Lumos, and we’re always looking to hear what sort of analytics tools would be useful to help improve your game.
I just integrated Lumos into my project. The reason I’m trying Lumos is because of the sandbox security settings with Unity, disallowing communication with Google Analytics. The major thing I see that’s missing in Lumos is the ability to log special events and average out values.
I’m writing a puzzle game and I want to get an average time that it takes for people to complete a puzzle. I can use a Debug.Log to spit out how long it took an individual user to complete a puzzle, and get that info… but I can’t do any sort of aggregate analytics. You really need that to be able to call it an analytics API, right now it’s just a remote logging API. I do see the potential in how easy it is to setup though.
Thanks! I’ve been looking for something like this. Though the functionality still leave a lot to be desired, I’m glad to find an analytic tool that cam be integrated very easily with Unity
I haven’t used it yet, but for a start, I want to log something but I don’t want to mix it with Debug.Log. I want to separate between Debug.Log that I wanna read during development, and maybe Lumos.Log , which will send the log to the server. Currently, I need to clean all the Debug.Log and only log something I want to see on the web, which isn’t really convenient.
Are you talking about custom events? Such as “Player beat level 1” or “Game over” and they would have a tally of how many times this event has happened, etc?
Custom events are in the pipeline. We realize it’s an important feature, and rest assured it’s at the top of our priority list. Along with the usability of the website, which admittedly leaves much to be desired.
Definitely send us any feedback and feature suggestions, it helps to know what sort of data you’d like recorded.
I’ve been using it for a few weeks now and I’m thoroughly impressed, caught a fair few errors already based on different platforms and such, not to mention just how easy the setup process is.
Definite recommendation from me if you’re releasing regular test builds as well, helps cut down on the number of “ok, and in what scenario is this bug occurring” emails with your guinea pigs.
Yes, custom events. Glad to know that it’s in the to-do list! Anyway, I just tried it and I have to say the integration and the process is very easy ^ ^ Kudos for that!
I don’t quite understand how the graph of new players work though. This is the first time I tried it with Lumos and while the statistic say 1 new player, the graph show 400 something in May. Is this just placeholder data or something?
I’m doing some Unity prototypes for the iOS platform. I have several Debug.Log commands and I’m seeing them in XCode console but they don’t come up in the Logs section of the lumos website. The feedback work fine though.
Should I be using Debug.Log or something else?
