A few things remain outstanding from last week's plans, but other things got accomplished that made up for them. At a very high level, the last 7 days saw the following:
1. Saw the first bug fix to live systems (server management stuff last weekend)
2. We got the Announcements content back up on www.playhawken.com (it's just text for now)
3. We're well on our way to identifying the cause and some fixes for long-standing mech problems and syncing issues; more work is needed, but there has been some good progress.
4. Our support site and operations are getting up to speed, so feel free to submit support tickets.
5. Source code looks to be in good shape
6. I read Hawken: Genesis. If you haven't, go get it; it's good.
7. New users can now access the server browser immediately
8. Server Region redesign is now live
9. New users now choose their default region the first time they play
10. Analytics systems are usable
11. Singapore Servers!
12 More Servers in Europe
Challenges:
1. Build systems will require a lot more work than I had hoped for to get them back up and running. It's going to be a pretty extensive rebuild of the old network. It's a matter of time though. But this is the big one.
Goals for this next week (they're fuzzier than in the past):
1. Release Steam Bundle
2. Work more on build systems
3. Roadmap and planning
4. Work on gameserver hosting improvements (better machines, cost)
5. Private server admin site
Remember,
Stress Test and 3x HC and XP:
Saturday and Sunday from 8am-12pm PDT (15:00 to 19:00 UTC).
Weekly Update - 2015-04-10
#1
Posted 10 April 2015 - 11:39 PM
- DerMax, crockrocket, Guns_N_Rozer and 6 others like this
~~Do not meddle in the affairs of dragons for thou art crunchy and go well with ketchup!!~~
#2
Posted 10 April 2015 - 11:45 PM
#3
Posted 11 April 2015 - 12:22 AM
#4
Posted 11 April 2015 - 01:15 AM
Great job guys and girls. I hope today's stress test goes well.
5. Private server admin site - Yes please! Awesomeness :)
- Dr_Freeze001 likes this
#5
Posted 11 April 2015 - 01:27 AM
(\__/)
(='.'=) This is Bunny. Copy bunny into
(") (") your signature to help him gain world domination XD
And if you dont ....
<-------------- ME and Bunny
#6
Posted 11 April 2015 - 02:05 AM
Amazing work. Thanks for keeping the community updated like this. We really appreciate it
![]()
The Atlas Of Illal https://community.pl...atlas-of-illal/
Illal Maps and Information https://community.pl...nd-information/
An Interview With Laila https://community.pl...iew-with-laila/
The Quarantine of Illal https://community.pl...ntine-of-illal/
#7
Posted 11 April 2015 - 03:01 AM
"Roadmap and planning"
i'm looking forward to this one the most.
"build systems" has to do with updates, right?
EDIT: Will the next update release the taunts that the tdm bots use (like that squatting dance)? Will the mech taunts be made global, like the paint jobs are currently (because there isn't enough taunts to have a unique one for all mechs)?
Edited by BismutZornisse, 11 April 2015 - 03:13 AM.
I have a lot of ideas and would like some feedback on them:
Suggestions for fixing things:
https://community.pl...of-suggestions/
Suggestions for new things:
#8
Posted 17 April 2015 - 04:36 PM
Great job! Just out of curiosity, do you get assistance or any information from the previous devs? It seems that there is a lot of puzzles and troubleshooting/fumbling through all the code thats necissary to get things back on track. Is there a way (if management decided on it) to throw some money at the old dev's for short term consult to explain the code and whats going on? It would seem that the time and money costs involved with rediscovering the sourcecode could be negated partially by allocating short term consultation costs for long term savings.
The sooner you get things humming, the sooer reloaded can profit from the product - and doesnt have to spend money for countless hours or months of employee time that could be used for more productive things. Eliminate the ramp-up period.
- comic_sans likes this
#9
Posted 18 April 2015 - 04:34 AM
Great job! Just out of curiosity, do you get assistance or any information from the previous devs? It seems that there is a lot of puzzles and troubleshooting/fumbling through all the code thats necissary to get things back on track. Is there a way (if management decided on it) to throw some money at the old dev's for short term consult to explain the code and whats going on? It would seem that the time and money costs involved with rediscovering the sourcecode could be negated partially by allocating short term consultation costs for long term savings.
The sooner you get things humming, the sooer reloaded can profit from the product - and doesnt have to spend money for countless hours or months of employee time that could be used for more productive things. Eliminate the ramp-up period.
This is why I'm such a stickler for writing readable code with thorough documentation and commenting. Too bad upper management rarely sees its value.
- TangledMantis likes this
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
Sign In
Create Account



Back to top













