The Hacker Project - a free online game

I've been looking into this suggestion, where you would be able to disconnect from last bounce server and continue actions from another end of your bounce chain.

- there is a new button now right of "Disconnect", named "D/C last bounce"

"D/C last bounce" will disconnect only the last node in the bounce chain. This enables you to re-use the bounce chain from an earlier node.

Seems to work just fine Emi.  Nice work!

LOL... Got the system down hit f5 message...  refreshed and this button popped up :)

Sounds good, however I must point out a side effect:

lolwut?

I had to reset the user bounce chains. If you where online, you need to redo the bounce chain.

Thank you.

Yeah, that's why I had to reset the bounces so it works correctly.

Ah, I did just that and it fixed it, before you replied.  :laugh:

Do I understand correct ? Does this mean I can start a few bounces at the start of the day and use this chain all day long ?
I'm not sure if that's a good thing for the game.

well its wrong on so many levels - but hey its an update so who cares

It's not necessarily bad...  It does leave lots of little traces for someone to come back to the original starting point...  If they have the correct undeleter for the first modified bounce.

It does remove the need for you to keep modifying the first log entry.

Oh, and I've noticed one difference when using the disconnect last bounce.

It forgets that you had admin access to the prior connection if that was the only access made.  It will again show the IP that it 'bounced' from.

I used to be able to get admin, bounce out and in again, and look at logs without showing that I'm still in system.  With disconnect last bounce it doesn't work that way anymore.

In addition, if you disconnect back to the first bounce connection, it will show your own server's IP in the log file since that is the previous bounced from on the chain.  Not a bug, but can result in you not realizing you just spammed your IP into the logfile.

I've been playing with the Disconnect quite a bit and so far it has worked great.  All the extra Admin Logged in from can be quite weird since they don't appear to be tied to a bounce connection if you've done it for a while, though.

ghost admin :laugh:

Yeah, but it's pretty easy for an experienced tracker to tail you by looking at the time stamp of the bounce. You'll notice the time does not change on the proxy bounce logs.

I don't really know why/where this update has come from considering all the other ideas that were out there, if anything its gave me more reason not to get a gold account  :19:

I use the admin logins to track newbies  :13:... They are the ones who don't bounce in and just connect directly to a server.  This will reduce that a bit  :shifty:

After using it ingame i like it ^^
Means i can accept a bunch of missions and do them all within one bounce, being lazy means they can all be traced by the root log though, but i have nothing to worry about from that, yet  :5:

Also spams server logs out nicely, should make a macro for that  :laugh:

Yeah, I've noticed that since this has gone in place I'm traversing 4-5 pages just to trace a bounce path...

lol just wait till someone has a 72 hour long bounce path - whatever is this world coming to

That someone being Ivan :)

72 pages maybe, not 72 hours  :13:
 
But you don't have to bother going through all of them ... finally got my logdeleter up to date  :5:

72 page of modified bounce logs?

No, not modified, just created by bouncing and using the new 'disconnect from last bounce' feature

what about the deleter?

Try undelete the logs I modified and you'll know what I mean  :laugh:

that is what  i meant when i said

OK never mind then, excuse my poor knowledge of english language

Irony?

Fair enough, we're getting updates so I won't complain anymore

exactly