My "last online" status isn't really much of an indicator - most of my work goes on via a dev on my computer, linked to a database on my computer. When I feel good about the amount of progress on a feature it gets uploaded to my keith.dev site, where other staff members (and sometimes users) can test it.

That means I can spend days working out of Asana (our task management software) and slack (our staff member chatting area) without touching the site. I get all of my bugs via Asana (where they are prioritized by most important to least important) and that's where I communicate with and the UAs on fixing user bugs, which I do mostly via directly working in the database, not on the site. We plan our site features and events in Asana, upload images to it, etc.

A lot of my time recently has been spent working on battle features (including the recently launched and then relaunched scroll library) and setting up new servers using HHVM which has required rewriting bits of older Subeta code (mostly items that use custom code, and instead switching them to functions) so that we can reduce our overall server bill and streamline our web servers. Those kinds of things get done without ever touching the site. I've also been playing with trying to restructure the "beta" (aka: way overdue) wardrobe into emberjs which means significantly less work in the long run but a TON of work making it happen in the short term. These are things that take a lot of time and testing on a personal server, and you won't see the benefits of for awhile (if ever in the case of the wardrobe because ember is HARD)

(Also - Alx hasn't worked for Subeta in 4+ years.)

Those things are in Asana, and are being worked on. There is progress on the wardrobe (and I just said I'm reworking it to work with Ember, that isn't what it uses now :)) and sometimes other things take priority. Auto fill is important, but if there is a critical bug that gets moved to the top of the list, it takes priority.

A lot of those bugs aren't even seen by most users, they're the kind of things that block accounts, remove access, and are things that the UAs need help with. It sucks, but they are more important.

- Impending summer event? What is this impending summer event you speak of? :x :x :x (secrets, we has them)

- I still play the game, but I work a lot more hours now. When I've talked to users they want so much more from me than what they used to, which I am not saying is unexpected or wrong, but I often feel that my presence in a colloquial sense is unwanted, so I've gotten a little quieter. I wish I could chat like I used to be able to! I've instead just been putting my focus into getting the art department's quality up and creating things for the users to love. I don't know, maybe eventually I'll develop tougher skin or I'll do enough to have the users happy having me around again, but at the moment I'm working on caring about this beloved site from a quieter perch. (But I will always be there to talk if people want to c:)

(Also, anon person - thank you. That was very much appreciated ;__;)

We actually haven't ported anything over in awhile. We're still working on the bootstrap branch (and can probably push it, I decided to instead keep both libraries and slowly move to bootstrap instead of just trying to rewrite all of the CSS on the site to match it). Bootstrap is just significantly more kept up than our existing library (semantic-css) and also has a lot more external and tool support.

As far as the javascript library, right now the wardrobe is using ... nothing. It's written in jQuery and just a bunch of AJAX calls which is fine for a smaller page (pages like achievements) but when you get into something as complicated as the wardrobe with so many moving parts, I think that generally it'd be better to let something like Ember do the heavy lifting, especially because the people building it are much, much smarter than I am in building these kinds of applications.

^. ember is just better written than anything I'll write. It's also complicated and written for entirely new sites, not to be sort of tossed into a site like Subeta on top of other stacks. It'll require having a page that only has your account information and not the sidebar (like the beta wardrobe now) because those things (old javascript) will interfere with Ember. It'll be much faster and easier to edit in the future, though, and Ember gets patches done to it on speed and data handling weekly, unlike code that I'd write that we'd push and probably not touch for awhile.

So the benefits to the users (and to the programmers who have to work on the wardrobe in the future) is MUCH greater than the cost of maybe trying to make it work and spending a week or two fumbling and decided that it isn't going to happen. Unfortunately if I have to make that call (and I have had to make that call a lot of times before) it means that I don't have anything to push.

Battle wasn't "pushed ahead" of other things. Battle was something we'd been working on for awhile (especially the instant loading) and we felt like it was a good opportunity to work on all of it and get it out. A lot of people who battle frequently are really pleased and happy they got that focus, and are one of the parts of the site that feel the most frequently ignored. The spotlight moves around the site and that time it didn't land on something you use that time.

I'm going to keep an eye on this thread but I hope that we've explained the OP well enough. We're working really hard on summer stuff now, so we have less time to respond to threads :)

- yes! That was something I/we tried for Peka-Boo last year, and I've been wanting to add those sorts of little touches to Subeta to make it more 'living'. This month it's obviously a mixture of Riverside, Veta and Peka, and...well there are a few other touches to be made to these maps and one of the maps that lead off from them... basically, I love the idea of actually having a visible night and day on Subeta, and all the potential it entails :D (Eventually I'd like to set up the times of the world so that night hits at different times for different areas, but just getting the visuals up first is pretty fun!)