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

Brief Update and Server Restarts

Greetings Hackers,

We have pushed a small update which includes a few small bug fixes. All of you Linux users will be happy to hear that we have fixed the chat bug which caused chat (on Linux) to freeze in certain circumstances.

Also, we have some news for you. The Dev team, starting today, will be performing bi-weekly server restarts, which may or may not include small bugfixes (similar to today's) or huge updates. We arrived at this decision due to the instigation of a member of the community, and also because of our wish to allow the community to see more activity from us, since you don't see all that we do behind the scenes. Rest assured, we are still working on HackWars, although development may seem slow at times.

Best Regards from the Dev team, and Happy Hacking!

Server Restart

Hackers,

The HackWars server ran into an out of memory error today. I strongly suspect !System!, but it would be hard to prove. Anyway, the server has been restarted. Apologies for the downtime.