Server Issues

Howdy Hackers,

The server crashed again recently. It has been restarted and I will start up the game server processes again. However, don't expect them to stay online, as there is apparently some kind of issue related to mysql. I will be pausing my work on other things to investigate this issue and solve it; hopefully that won't take too long. In the meantime, please be patient and we apologize for any inconvenience.

- TTJ and the dev team

It wasn't me

Haha! Ok, so at some point our database went nuts and the server facepalmed causing everything else to do a few barrel rolls. I'm still not 100% sure at this point what's been going on. However, I kicked the MySQL box a few times and we got some response. While it seems as though the game is fairly operational at this point, I'm pretty sure it's a bit unstable. We may lose a wheel around the next turn.

That being said, chat is borked. (Yes, borked.) By unstable I mean there's a possibility of losing progress at this point in your save state so, don't do anything extreme until we get this sorted out. Chillax, get some hacks, cash and exp but don't work yourself over it.

For those that find it unacceptable for accidents to happen; you've been warned. No goodies will be given out if you hack the planet and it doesn't get saved. ;)

Jan 15th update

Hey guys, We ran an update tonight and there is one small change included. We've changed the CPU usage formula for when using a damaged attack port. On the old system it was a linear 1:1 ratio so that every 1 health point you lost the port uses an additional 1% of the maximum CPU load of your system. With the new system it is not longer as linear. With the starting CPU the usage will remain linear, however with each new CPU you buy the formula becomes slightly less linear. We've included this on an experimental basis. In theory it should make it a little easier to run multiple attack ports at once or include an extra watch while you attack. We realize that things may not be perfectly balanced at first, so we'd like some feedback as to what players think. If things have become to easier or to hard please let us know so we can adjust the rates.
You can see a picture here of an example of the new % CPU usage vs the old % CPU usage.

Image and video hosting by TinyPic

-The HackWars Dev Team




Happy (Late) New Year!

Hello Hackers! Chris a.k.a. DraconisRavenix here to wish you all Happy (late) New Year! We have some massive changes coming up behind the HackWars franchise to put us on the map as more than just a blip on the net.

During upcoming weeks everything HackWars will be undergoing some serious changes. We have a couple of announcements to kick off 2012. As we’ve already seen a couple small changes in action from Joe and Nick with the aid of Matt (a.k.a. Bastard), a few more updates are on the way. Matt’s recreation of the network map along with Nick and Joe’s consistent hard work behind the code were just small taste of things to come. NPCs are on their way to yet another jump to not only facilitate needed changes and balancing but to also (semi)finalize HackWars official content.

HackWars will be leaping forth with a coded from scratch sequel; HackWars 2.0. We know the current HackWars is “incomplete” and “broken” however, in order to complete and fix HackWars, it has been at the point of requiring a major rewrite anyway.

More information will be released as days go by getting closer to milestones which are being put into place as we speak. Until then and during this time... happy hacking.

Updating the Nets

Hackers,

We apologize for interrupting the bi-weekly restart schedule, but we felt that we could not hold back the few updates that have been introduced tonight any longer. The bug whereby players under level 30 did not receive quest money rewards has been fixed. The network map has been redone based on a layout by the player "bastard" inspired by developer Draconisravenix's inital concept, and we feel it looks a LOT nicer. In addition, moving between networks has been fixed and now should work as it was intended to. Briefly, this means that you can only travel from one network to another if they are adjacent.*** If you have any comments, questions, suggestions, or bug reports associated with the update, please post them in the comments, for example, reporting strange behavior in moving between networks. Happy Hacking!

Sincerely,
Your Dev Team

*** There may be unmarked shortcuts between networks which are not adjacent