Vampiro Claro cheat?

[_dracus_]

I can't understand where is the fun in killing the process, you still need to launch it again, type your passwoard, and everything this is stupid. You give RP sometimes, ok, then try to work out how getting some.

[bastila]

I crash a lot with the linux client, which is in effect the same as killing the process.

For every crash, if I am being attacked before the crash, I cannot login again before I am dead or the mob that was attacking me was killed. Same goes with players attacking me. I always relog in when being attacked before the crash at the save.

Try this. Buff up then attack the weakest mob possible so that it takes a long time to kill you even if you don't attack back. Kill the process once being attacked. You'll notice that when trying to connect the same character a message comes up telling you that this character is already in the game and asks if you want to send the report to NGD. This goes on until your character is dead.

This leads me to think something else is being done other than just killing the process.

Regards

[amade]

Originally Posted by bastila

Kill the process once being attacked. You'll notice that when trying to connect the same character a message comes up telling you that this character is already in the game and asks if you want to send the report to NGD. This goes on until your character is dead.

This leads me to think something else is being done other than just killing the process.

Many times I crash and when I want to login I don't get that error report send option. Could there be a difference between the two?

At any rate, this thing is becoming despairingly widespread now :\

[bastila]

• If I crash while being attacked the "character already loged in" message will always come up. The only way the error message is not there, is that my character is not attacked anymore (aka dead). Also if I am being followed by aggro mobs and crash, those aggro mobs will kill me as well.
  
  
• If I crash and was not being attacked before it, I can log the character in again relatively fast without message. That is only if I wait a few seconds before doing so. I crash very fast out of the game, and the client loads real quick, meaning I can be on the character selection window in 9-12 seconds. If I try to login the character under ~15 seconds, the same error message shows up telling me that the character is already connected.

This behavior clearly demonstrates the use of a timer that stops my character from loging out for a set amount of time. Also if I am being attacked before the crash the timer keeps on reseting before the character is released from the gameworld (character is dead, not being attacked anymore).

Amade: It might be that you are not trying to log in your character fast enough and the character is already released from the game so you don't have the "character already loged in" error message.

A crash never does me any good. The only way I survive is if the enemy is far away and cannot get in range of me before my character is released. Enemy in range or close to be in range; I'm dead every time.

Even buffs such as sanctuary are removed upon killing the client. A conjurer and I tested it the other day. She cast sanctuary and then killed the client. Sanctuary remained for a couple seconds, then she was for ~4 seconds without sanctuary (animation of sanct also disappeared) where I was able to cast synergy bond on her. After the 4 seconds the character was then released.

From what happens to me with the crashes, I can say that just killing the client would not behave in the way some people are disappearing while being attacked or in sanctuary.

Regards

[NightTwix]

Originally Posted by bastila

I crash a lot with the linux client, which is in effect the same as killing the process.

For every crash, if I am being attacked before the crash, I cannot login again before I am dead or the mob that was attacking me was killed. Same goes with players attacking me. I always relog in when being attacked before the crash at the save.

Try this. Buff up then attack the weakest mob possible so that it takes a long time to kill you even if you don't attack back. Kill the process once being attacked. You'll notice that when trying to connect the same character a message comes up telling you that this character is already in the game and asks if you want to send the report to NGD. This goes on until your character is dead.

This leads me to think something else is being done other than just killing the process.

Regards

thats how it behaves for me, too.

but theres no doubt that theres a way to logout fast even while under fire.
maybe it works for the windowsclient only?

[Tyr]

Originally Posted by NightTwix

but theres no doubt that theres a way to logout fast even while under fire. maybe it works for the windowsclient only?

No that is the way it works for me as well using the windows client. You are correct there seems like there is a way to do this but simply killing the process is not it.

[amade]

Originally Posted by bastila

Amade: It might be that you are not trying to log in your character fast enough and the character is already released from the game so you don't have the "character already loged in" error message.

No, you misunderstand me :P

I meant that usually when you crash the launcher prompts you to send an error report. Sometimes, quite often actually, I crash and when I try to login I will not have the option to send in the report. And always my character will never still be in the game when this happens. I'm not a technical sort of person, but the crash/end process whatever it is called is different from the usual crashes where you'd be prompted to send an error report.

For a more detailed description, the crash where I would be prompted to send an error report later is usually sudden. My game would suddenly just quit and an error message will come up. The other sort of crash is where the game hangs but does not quit, so I have to click the X button to end the process (a message box asking me to confirm to end process would come up).

[chuckclose1]

Originally Posted by amade

No, you misunderstand me :P

I meant that usually when you crash the launcher prompts you to send an error report. Sometimes, quite often actually, I crash and when I try to login I will not have the option to send in the report. And always my character will never still be in the game when this happens. I'm not a technical sort of person, but the crash/end process whatever it is called is different from the usual crashes where you'd be prompted to send an error report.

For a more detailed description, the crash where I would be prompted to send an error report later is usually sudden. My game would suddenly just quit and an error message will come up. The other sort of crash is where the game hangs but does not quit, so I have to click the X button to end the process (a message box asking me to confirm to end process would come up).

amade you r correct 100% that is how it happens when the game crashes unexpectedly when u log back in you are given the option to send an error report to ngd studios,

whowever i think older operating systems dont support that feature