AntiKS System

[leeploper]

Wow this is amazing O_O I've never seen anything else like it. It still sucks if you have someone in your map and they just kill monsters that you haven't gotten to yet though.

 

[kevintjuh93]

Nice release although I think this is useless though. Well maybe because I am a GMS die-hard.

 

[hindie]

is this related to moongrams's work ? i heard they had their antiks system too

 

[ImReplay]

That will make game peaceful without KS, :2

 

[Emilyx3]

is this related to moongrams's work ? i heard they had their antiks system too

Nope, this is my original work. If they have an antiKS, they implemented it differently. I don't steal/leech things and claim it as mine >_>

 

[XxОsirisxX]

is this related to moongrams's work ? i heard they had their antiks system too

MoongraMS "AntiKS System" doesn't works like this, and I hope it doesn't. It's more manual.

Really creative idea tho, nice job.

 

[~Delta]

I should be the one asking you, to me you are being stupid when you say yourself a pro and feels that you are 90% better than the community.

Just leave him in his dreams.

 

[Defcon]

cool never seen before nice release

 

[eternalms]

agreed, very nice thank you.

 

[Hennessy`']

Does this works for anyone else? I implemented and It didn't work, activated AntiKS but They can still KS. Might be i added wrong, but Anyone tested yet?

 

[eternalms]

Does this works for anyone else? I implemented and It didn't work, activated AntiKS but They can still KS. Might be i added wrong, but Anyone tested yet?

lookie at the first line in case you tested it on a gm account

if (monster.getBelongsToSomeone() && monster.getBelongsTo() != player.getId() && !player.isGM()) {
    player.dropMessage("You cannot hit this monster because it belongs to someone else.");
    continue;
}
if (player.getAntiKS() && antiKS < 3 && monster.getCanBelong() && player.getNumAntiKSMonsters() < 10) {
    monster.setBelongsTo(player);
    antiKS++;
}

 

[Hennessy`']

lookie at the first line in case you tested it on a gm account

if (monster.getBelongsToSomeone() && monster.getBelongsTo() != player.getId() && !player.isGM()) {
    player.dropMessage("You cannot hit this monster because it belongs to someone else.");
    continue;
}
if (player.getAntiKS() && antiKS < 3 && monster.getCanBelong() && player.getNumAntiKSMonsters() < 10) {
    monster.setBelongsTo(player);
    antiKS++;
}

Nah, I thought of that earlier. I de-gmed myself, and my other testing char.

 

[eternalms]

honestly i don't have a test character, i implemented it but never really tried it. Ill look into it now

 

[Hennessy`']

honestly i don't have a test character, i implemented it but never really tried it. Ill look into it now

Thanks, Please tell me if it works.

 

[eternalms]

Wow tried it , doesn't work . I'ma go over the code maybe im missing something thats being stated ;o

 

[Hennessy`']

All these good Comments, but noone tested it? Hmm..

 

[Emilyx3]

Sorry guys, I corrected the error.
I had

public boolean getBelongsToSomeone() {
        return belongsTo != -1 && endBelong < System.currentTimeMillis();
    }

instead of

public boolean getBelongsToSomeone() {
        return belongsTo != -1 && endBelong > System.currentTimeMillis();
    }

=( Stupid less/greater than signs.

Also, You should readd the AbstractDealDamageHandler addons, I didn't remember to increment the player's antiKS num, so the player would be able to control as many monsters as he/she wanted.

Correct version is in my first post. Let me know if you find any more bugs.

 

[Shawn]

lookie at the first line in case you tested it on a gm account

if (monster.getBelongsToSomeone() && monster.getBelongsTo() != player.getId() && !player.isGM()) {
    player.dropMessage("You cannot hit this monster because it belongs to someone else.");
    continue;
}
if (player.getAntiKS() && antiKS < 3 && monster.getCanBelong() && player.getNumAntiKSMonsters() < 10) {
    monster.setBelongsTo(player);
    antiKS++;
}

Please learn what an Operator is...

!player.isGm() is checking to see if they are NOT a GM. So, that message would only show up if they were not a GM.

 

[RMZero213]

Please learn what an Operator is...

!player.isGm() is checking to see if they are NOT a GM. So, that message would only show up if they were not a GM.

The way I saw the situation, the system wasn't working (the message would be, one way to check if its working), and he told the other person who didn't have it working to check if they were on a GM. So it would make sense if it didn't work, in case they were GM.

Of course that wasn't the case.

 

[eternalms]

The way I saw the situation, the system wasn't working (the message would be, one way to check if its working), and he told the other person who didn't have it working to check if they were on a GM. So it would make sense if it didn't work, in case they were GM.

Of course that wasn't the case.

someone that can actually read what i said correctly.