BuzzerBeater Forums

BBAPI Support > Potential

Potential

Set priority
Show messages by
This Post:
00
141462.6 in reply to 141462.4
Date: 4/21/2010 7:07:42 AM
Overall Posts Rated:
9999
Hmm, but hall of famer potential is 10 too....

This Post:
00
141462.7 in reply to 141462.6
Date: 4/21/2010 7:08:53 AM
Overall Posts Rated:
3737
Hmm, but hall of famer potential is 10 too....


Right. That's a different question.

This Post:
00
141462.8 in reply to 141462.3
Date: 4/21/2010 7:14:42 AM
Overall Posts Rated:
3737
Here's a long shot, but maybe the potential for ATGs shows up differently when it's one's own roster, and not someone else's? I can't test that with my own.

This Post:
00
141462.9 in reply to 141462.8
Date: 4/21/2010 7:21:06 AM
Overall Posts Rated:
9999
I guess the same, there must be a difference between all-time great and hall of famer. I have no player like one of these, so I can see only others. But in every case, the owners try to update the players datas so they must get the longest xml with skills and etc. They got false for the criteria which I wrote above....I got true, when tried to get these player's xml as outsider.

From: Kukoc

This Post:
00
141462.11 in reply to 141462.10
Date: 4/21/2010 11:37:39 AM
Overall Posts Rated:
13361336
Not so long ago XML also showed max game shape at 8, although it was actually 9. Same with season start xml showed 6, although it was 7. Perhaps it's the same with potential. Max is actually 11, but xml shows it at the top end of 10?

This Post:
00
141462.12 in reply to 141462.10
Date: 4/21/2010 11:49:08 AM
Overall Posts Rated:
3737
Thanks for that, that's the crucial datum to put the problem on urimate's side. Sorry, urimate.

This Post:
00
141462.13 in reply to 141462.11
Date: 4/21/2010 11:54:37 AM
Overall Posts Rated:
3737
Not so long ago XML also showed max game shape at 8, although it was actually 9. Same with season start xml showed 6, although it was 7. Perhaps it's the same with potential. Max is actually 11, but xml shows it at the top end of 10?


I've started a new thread on this to keep the two issues distinct: (141496.1)

This Post:
00
141462.14 in reply to 141462.12
Date: 4/21/2010 12:50:53 PM
Overall Posts Rated:
9999
Ok, I understand...but somebody should say where the problem is... :D

This Post:
00
141462.15 in reply to 141462.14
Date: 4/21/2010 1:49:56 PM
Overall Posts Rated:
3737
Ok, I understand...but somebody should say where the problem is...


Well, you've got a lot of help here already. You need to step up and do some more detailed debugging on your side to sort out what's wrong in (141462.3).

Here's another longshot, but in the code (or pseudocode) you posted, is your comparison of the potential actually numeric? You posted > '6' (in single quotes). 10 > 6, but is '10' > '6' in whatever you're coding in?

Last edited by Mod-oeuftete at 4/21/2010 1:50:18 PM

This Post:
00
141462.16 in reply to 141462.15
Date: 4/21/2010 2:17:08 PM
Overall Posts Rated:
9999
It is PHP, and yes, '10' > '6' gives true (it works with haal of famer potential), that's why I thought that all-time great is '10+' or something like that, because '10+' > '6' gives false.

And as I said, this works fine with most of the players except for the players with all-time great potential....

This is a function, which checks that the player is good enough for the hungarian U21 NT or not. It returns with true, if he is or false, if not. It is qiuet simple, only checks his age, salary and potential. Lot is users in Hungary used it in the last week, without any problem (or they don't alert me, if there was any problem) until today, when one of them wrote, that it said his player is not good for the NT, but it is not true (and this user has right). I checked the code and find, that under his age, salary....etc. he should be good enough...


Advertisement