Planetarion Forums

Marka · 22 Aug 2006, 23:02

No clue why it was disabled - if it was a bug, happened accidently or intentionally.
So far 3 ppl from our alliance have lost roids to attacks that never should have happened if the limit was as it is supposed to be.
Shouldn't be too much of a hassle to fix as it is basically the same as Value Bashlimit that is still intact.
I am still wondering why there hasn't been any anouncement about it - Support was notified more than 12h ago and promised to look into it.

No need to make it even easier for the top planets as it is this round anyway

Regards
Marka

Kal · 22 Aug 2006, 23:20

We have not been able to reproduce this bug in testing and we cannot see any potential issues in the code. If anyone does encounter it please get in touch as fast as possible with full details.

Chika · 22 Aug 2006, 23:25

well the round is over pretty much anyway, and you won't end much higher or lower. People are probably doing the resource spend thing.

Marka · 23 Aug 2006, 00:01

Quote:

Originally Posted by Kal

We have not been able to reproduce this bug in testing and we cannot see any potential issues in the code. If anyone does encounter it please get in touch as fast as possible with full details.

Err - what evidence you need exactly?
I have had half a dozen ppl try attacking planets that are above 40% their value but less than 60% (50%, 40%) of their score.
I have the impression that everyone can do that atm - noone I asked could see planets with orange score.
If you need JGP or anything to proof that leave me a Forum Message or contact me on IRC.

Vikman · 23 Aug 2006, 02:49

I see the orange values on planets just fine.

Kal · 23 Aug 2006, 07:17

Quote:

Originally Posted by Marka

Err - what evidence you need exactly?
I have had half a dozen ppl try attacking planets that are above 40% their value but less than 60% (50%, 40%) of their score.
I have the impression that everyone can do that atm - noone I asked could see planets with orange score.
If you need JGP or anything to proof that leave me a Forum Message or contact me on IRC.

A JPG is not relevant - only tyhe score/value when the order is given matters. So you would need a screen shot or something showing the score and value of the target a the approxmate mission order time.

And again if we can't reproduce the bug or see any issues in the code then clearly we cannot fix it.

coffee- · 23 Aug 2006, 09:11

I think possibly the confusion is that this bash limit allows you to hit someone if value is within the limit, OR score is within the limit, OR value and score is within the limit?

Marka · 23 Aug 2006, 10:37

Quote:

Originally Posted by coffee-

I think possibly the confusion is that this bash limit allows you to hit someone if value is within the limit, OR score is within the limit, OR value and score is within the limit?

According to pre-round infos, manual and #support it should be value AND score.
I left Kal some examples where ppl been able to set attacks on planets as low as 13% of their score or 72% of score but 18% of value.
Check for yourself if you can attack planets that are above 40% of your value but below 60% of your score or attacking planets above 60% of you score but below 40% of your value.
To me it appears as if the AND check has been replaced by OR check.

The Real Arfy · 23 Aug 2006, 10:53

Quote:

Originally Posted by Marka

According to pre-round infos, manual and #support it should be value AND score.
I left Kal some examples where ppl been able to set attacks on planets as low as 13% of their score or 72% of score but 18% of value.
Check for yourself if you can attack planets that are above 40% of your value but below 60% of your score or attacking planets above 60% of you score but below 40% of your value.
To me it appears as if the AND check has been replaced by OR check.

No. The whole point of implementing it was so that XP-whores with value under a planets bash, but with a high score could be hit. Thats why its obviously an "OR check" as you put it.

P.S. I definately read that in the manual, it was no mistake.

Wandows · 23 Aug 2006, 11:11

Quote:

Originally Posted by Manual - Missions

Please note, you cannot attack planets which are less then 40% of your value AND score.

Quote:

Originally Posted by Round 18 Announcement

The "bash" limit (i.e. smallest planet you can attack out of protection and so forth) is 40% of your own value and 60% of your own score.

As far as i can see it is meant to have both above the %-tage before being able to attack that target (stated by the 'AND'). Not that i agree to have it that way (i much rather have it the 'OR' way), but i can't find any place in the manual which states otherwise. And ofcourse the question is what is right, the manual, or the announcement (i suppose it's the announcement).

Kal · 23 Aug 2006, 20:29

In order for a planet to be below the bash limit its value has to be less than 40% AND its score less than 60% of the attacker. This is what is intended, this is what is in the manual, and this is what the code does. The examples Marka has shown me all comply with this logic.

GReaper · 23 Aug 2006, 23:04

I'm afraid the manual is inaccurate, check the missions page.

Quote:

Please note, you cannot attack planets which are less then 40% of your value AND score.

Which confused me quite a bit when my own galaxy browser and sandmans were giving different results for planets I couldn't hit.

myk · 23 Aug 2006, 23:17

Marka, I promised I would look into it and I did. The reason for there being a lack of an announcement is because there is nothing wrong with the code. Not only have I come to this conclusion but others who have looked at it, also have.

The code perfectly reiterates what was previously posted in the Round 18 Announcement at the beginning of the round and that is:

The "bash" limit (i.e. smallest planet you can attack out of protection and so forth) is 40% of your own value and 60% of your own score.

Remy · 24 Aug 2006, 14:54

Quote:

Originally Posted by Chika

well the round is over pretty much anyway, and you won't end much higher or lower. People are probably doing the resource spend thing.

The resource spending thing was disabled...

rshih · 24 Aug 2006, 16:21

nope.. can still do it, jus can't get all of your res back. Have to actually prod out real ships now

Appocomaster · 24 Aug 2006, 16:50

Quote:

Originally Posted by GReaper

I'm afraid the manual is inaccurate, check the missions page.

Which confused me quite a bit when my own galaxy browser and sandmans were giving different results for planets I couldn't hit.

Yes, it is sorry. It was 40 and 40 last round, it was changed back to 40 and 60. I've corrected it.

ChipZ^ · 25 Aug 2006, 17:19

Quote:

Originally Posted by Appocomaster

Yes, it is sorry. It was 40 and 40 last round, it was changed back to 40 and 60. I've corrected it.

I dont see anywhere in the manual where its been "corrected".

Also the game is coded for 40% value OR 60% score.

Atm my value bash limit is ~900k but i can happily attack 600/700k planets with high xp.

Appocomaster · 26 Aug 2006, 20:09

No.
In the manual it says

"Please note, you cannot attack planets which are both less then 40% of your value AND 60% of your score."
that means you can attack planets that are only one of them, logically?

rop1964 · 29 Aug 2006, 00:13

actually, score is irrelevant as to bashing.. as someone with 5 million of score but 1million in value would still bash a planet of 400k value..

the key is value.. something must be done to dissuade or penalise basher.
i have suggest to put in a negative score penalty , leveled from 60% of value down to 40%, so if someone try to bash a planet , he lose score according to the level of bashing he d do.

i propose 1k score loss for each 1k of roid/ship value stolen. down to 2k per roid/ship stolen at 40%. so if a million value guy attack a 40% vale target , he get max penalty. top player looking to win the game would not be so quick to attack weak target.