俱樂部資訊
統計數據
| 全部勝場/比賽 | 153/260 59% |
Titles
 |
 |
 |
|
|---|---|---|---|
| 國際聯賽 | 0 | 1 | 1 |
| 國內聯賽 | 1 | 0 | 1 |
| 合計 | 1 | 1 | 2 |
重大成就
United States.2.1
|
 x 1
|
World League.4.8
|
31 名次 x 1 |
84 賽季
|
United States.2.1
|
|
|
World League.4.8
|
31 名次 |
83 賽季
|
United States.2.1
|
5 名次 |
|
World League.5.15
|
|
4.4
+22
Could you explain more about this one:
"various skills’, tactics’, tiredness calibrations" -- 83 賽季 63 天
"various skills’, tactics’, tiredness calibrations" -- 83 賽季 63 天
--
(翻譯)
(翻譯 EN)
+5
As we mentioned in the article - we needed to completely rewrite some parts of the engine. So a lot of formulas needed to be changed as well. Basically most parts of the match engine had some changes (bigger or smaller) and it is not possible to write everything in details. And in the upcoming few seasons we hope to balance everything.
--
83 賽季
63 天
--
(翻譯)
(翻譯 EN)
+1
+0
It would be nice if you could give at some point give us an idea of what these changes are so we are not in the dark relearning the mechanics of the game
--
83 賽季
63 天
--
(翻譯)
(翻譯 EN)
+5
I’m happy to hear about the improvements you’ve made and anxious to learn more about the system in order to strengthen my team!
--
84 賽季
1 天
--
(翻譯)
(翻譯 EN)
+3
How about friendlies? Will the new match engine be used for friendlies as well, or is it only for national leagues right now?
--
84 賽季
1 天
--
(翻譯)
(翻譯 EN)
+2
1.1
What about improving actual draft??? It is horrible and no one likes it!!!!!! Come on listen to the community!!!
--
84 賽季
1 天
--
(翻譯)
(翻譯 EN)
+26
Also could you bring back the function where teams were able to borrow two players. ? I think that one Romanian player who complained left the game , so we good , aren’t we ?
--
84 賽季
3 天
--
(翻譯)
(翻譯 EN)
+5
Hi, I believe we all get PM message. I have one question abiut my game. Does it mean my NL game (will start at 18:00 game time) will be with the old engine?
--
84 賽季
5 天
--
(翻譯)
(翻譯 EN)
+0
I believe admins should cancel all tiredness for players from NL games today. I was making taktics no matter of tiredness today just for analysis of new tactics, but there is no feedback about it. Also all teams who had games with new tactics have many players with big tiredness (as far as I know). So I believe it would be fair to cancel all tiredness for players today
--
84 賽季
5 天
--
(翻譯)
(翻譯 EN)
+13
1.1
I watched my game with new engine and although I lost the match with 18 points difference, I liked the new in-game events and I believe it is more realistic; the tiredness issue could be reconsidered of course; but I hope the new engine is applied again in short notice; thanks for the design, I believe it is bug-free...
--
84 賽季
5 天
--
(翻譯)
(翻譯 EN)
+2
So what about players condition? It not honest that someone will play today with old engine.
--
84 賽季
5 天
--
(翻譯)
(翻譯 EN)
+0
1.1
Just wondering if it is expected to have 30+ fast breaks with fast break set to rare, since I got less than 10 fast break normally with the same tactic setting in old engine. And also it is expected to have the successful rate of fast breaks increased significantly, isn't it? Just want to make sure they are not bugs
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+0
Also it's kinda strange, when only 4 seconds pass, but player somehow do 3 seconds violation. :)
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+1
Today we also had a few problems that led to some youth matches being played with the new testing engine. That was not intentional and now it is switched back to the regular one.
Few users expressed opinion about ignoring tiredness in training - however that is not possible.
Currently our main goal is to fix bugs (such as
marcinkus just reported. Thank you!)
Then we will go with various calibrations.
As for fast-breaks , it almost did not exist in the previous engine. So yes - we should have more of them in the new testing engine. But currently we probably have too many of them. So in the final version we hope to be somewhere in the middle. -- 84 賽季 8 天
Few users expressed opinion about ignoring tiredness in training - however that is not possible.
Currently our main goal is to fix bugs (such as
marcinkus just reported. Thank you!)Then we will go with various calibrations.
As for fast-breaks , it almost did not exist in the previous engine. So yes - we should have more of them in the new testing engine. But currently we probably have too many of them. So in the final version we hope to be somewhere in the middle. -- 84 賽季 8 天
--
(翻譯)
(翻譯 EN)
+6
A stranger thing in my Youth League match : some action are realised by players who are not on the court (especially deflection)
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+0
It’s good that tiredness got increases, but one still should be able to to play 30mins . Hope it’s not final adjustment on tiredness , also not fixing the market before putting new engine to international leagues would be massive mistake .
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+1
比賽zaidejas kazkodel sugalvojos pailseti
https://www.basketpulse.com/lt/Player/1997304/description
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+0
1.1
比賽1 kėlinys
9:11 žingsniai. Po 5 sekundžių kitoje aikštės pusėje 3 sekundžių pažeidimas. Dar po 2 sekundžių vėl kitoje aikštės pusėje daromas prasiveržimas (nebuvo greito paso į priekį) Manau gerokai per greitai vyksta įvykiai. Panašių įvykių buvo daugiau tarkim po baudų metimų (pataikyti) praėjus 2 sec. įmetamas tritaškis kitoje pusėje. (1 kėl. 1:35) -- 84 賽季 8 天
--
(翻譯)
(翻譯 EN)
+1
比賽Fouled out player playing 57 seconds more bug occurred in my today’s match too with new engine; I wrote it as a message to administration... -- 84 賽季 8 天
--
(翻譯)
(翻譯 EN)
+0
Also, if we adding more actions, can we add what kind of foul it was, from 2pt zone or 3 pt zone? Because when you watching live, you just waiting to see, it will be 3 free throw or just 2. Especially in game last minutes, when every point is important.
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+5
1.1
Also with me the player D. Schröder remained after its 5. foul still up to next play interruption on the field.
4Q 7:32 LEI Defensive foul during a drive to the basket (5 f ): D. Schröder
4Q 6:59 LEI Substitution out (fouls' limit exceeded): D. Schröder ( SG)
( 比賽
The impressions that some events happen too early (illogically), I can confirm. For example 3 seconds violation with 4 seconds played time.
The success rate of the fastbreaks is much too high in my opinion. Here for example a game with a total of 64/64 fastbreaks.
比賽
In addition, the players should tire faster with many fastbreaks.
I don't have that impression. Especially if you compare a slow pace tactic against a fastbreak tactic. The fatigue of the players of both teams is comparable at the end. That makes no sense. For example in this game: 比賽
--
84 賽季
8 天
4Q 7:32 LEI Defensive foul during a drive to the basket (5 f ): D. Schröder
4Q 6:59 LEI Substitution out (fouls' limit exceeded): D. Schröder ( SG)
(
比賽The impressions that some events happen too early (illogically), I can confirm. For example 3 seconds violation with 4 seconds played time.
The success rate of the fastbreaks is much too high in my opinion. Here for example a game with a total of 64/64 fastbreaks.
比賽In addition, the players should tire faster with many fastbreaks.
I don't have that impression. Especially if you compare a slow pace tactic against a fastbreak tactic. The fatigue of the players of both teams is comparable at the end. That makes no sense. For example in this game:
比賽
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+0
Unsportmanlike fouls; technical fouls and disqualifications may add fun and excitement too if possible...
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+0
00:4210 : 17ŠBSPataikyta bauda: Ž. Niaunys (2 tašk., 2/2 Baudų m.)K1 00:40 PVNepataikytas tritaškis: A. Barragán (Bloga situacija; 3/4 Trit žiūrėkit kaip nori per dvi sek išsimetus kamuoli metimo nepadarysi. Plius manau baudų pataikymas per daug sumažintas. Arba reik gražint prieš tai buvusius žaidėjų skilus kai buvo bauda ir vidutinis atskirai
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+1
pirma antro kelinio ataka , varžovai nesugebėjo pereit vidurio linijos per 8 sek. bet pirmoj atakoj kamuolys išmetamas iš šono ne iš galo. ta praktiškai neįmanomas variantas nepereit
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+0
Po priešininko taiklių baudos metimų duoda atakai 14 sekundžių.
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+0
Taip pat ir po greitos atakos. Turiu screenshota, bet nežinau kaip įkelti...
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+0
Su nuovargiu tai kažką darykit, nes ryškiai perspausta, kai net 20min negali sužaisti žaidėjas...
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+2
normaliai tas nuovargis, nereikia pensininku vaikyt greitom atakom... jauniem ir sveikiem nekyla tokiu bedu... bet siaip nelabai patiko tas nuovargis
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+0
比賽 both teams make fast breaks 100%, Marcinkevičius, who foul out in the middle of 1Q, make „ghost“ appearance and tip the ball in first seconds of 2Q and then disappears again. And often after fast break, arrow, which shows who have the ball at the moment, stays in the same side and give 14 seconds to attack the basket to other team.
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+0
Šiaip reziume reikėjo adminams bent vienas rungtynes patiems pasižiūrėti, nes kas čia vyksta pažiūrėjus du kėlinius tai yra kosmosas.
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+2
1.1
Partidos both teams make fast breaks 100%, Marcinkevičius, who foul out in the middle of 1Q, make „ghost“ appearance and tip the ball in first seconds of 2Q and then disappears again. And often after fast break, arrow, which shows who have the ball at the moment, stays in the same side and give 14 seconds to attack the basket to other team.
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+0
We will have to wait to draw more conclusions, but there is no doubt that an explanation is needed about what you want to present with this new engine because at first glance it is difficult to understand
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+1
Tragic situation with tiredness in new engine low tempo, relaxed defence and in 33 min tiredness is 87. Ok i agree tiredness should play bigger role, but now even 17 min player gets tired in low tempo game. For youth teams we also cannot have suvh engine - we have training plans for players and with such, they lose points. Maybe administration decides we cannot raise players by giving play 40 min, but this should be well known in advance. We can test engine in national league, but this should not be ruining our players! Also why we dont use the additional matches gor testing as we used to? 比賽
--
84 賽季
8 天
比賽
--
84 賽季
8 天
--
(翻譯)
(翻譯 EN)
+16
Totaly agree to Lape. Its not big deal to loose national but player get tired and had ingurys in wl. Also can't pratice normaly. Why cant we test engine with national teams first?
--
84 賽季
9 天
--
(翻譯)
(翻譯 EN)
+1
1.1
1)The new match engine has physical problems. Players are easy to get tired. Old players can only play for 10-14 minutes. As a result, many tactics can not be used, such as fast, man to man, fast break, press, go all out to grab the front rebounds, not to mention the whole court press tactics. I hope you can adjust back to the original physical mode.
2)There are many traveling violations in the game, which should be related to the players' dribbling. But we think it depends on the location. For example, PG's dribble can require a high point, and PG's dribble pass line is 10. SG / SF dribble pass line is 8. The dribble pass line of C / PF is 6. Would that be more reasonable? -- 84 賽季 9 天
2)There are many traveling violations in the game, which should be related to the players' dribbling. But we think it depends on the location. For example, PG's dribble can require a high point, and PG's dribble pass line is 10. SG / SF dribble pass line is 8. The dribble pass line of C / PF is 6. Would that be more reasonable? -- 84 賽季 9 天
--
(翻譯)
(翻譯 EN)
+3
Is tiredness linear with respect to play time in new engine? 24 mins even on slow pace and zone defence is 60% already. Maybe make it exponential and average threshold to over 50% tired is around 30 min? Whichever will balance things out and not get players tired just playing little over 20 mins even on minimum effort.
--
84 賽季
9 天
--
(翻譯)
(翻譯 EN)
+0
If it is a way to force users to jave more players in teams well then it might work, just had to bring one in as 2 of my players got injured...
--
84 賽季
9 天
--
(翻譯)
(翻譯 EN)
+0
Well, i am super happy to see, how other users complaining about tiredness. Finally, we will kick out teams with 7-8 players, that is absolute nonsence in this manager. I always was interested to use 10 or even more players in every match, but i was forced to have just 7-8 players not to lose game. That was nonsence, when gold medals in both leagues were collected by team with 7 players. This was creapy, i tried to discuss about that, but i was told, this is nba playoffs style to use less players. Of course, there are somw bugs, that need to be fixed, but not a tiredness. Thats perfect. This is just my opinion.
--
84 賽季
9 天
--
(翻譯)
(翻譯 EN)
+6
Yes , I agree with puntukas that it was necessary to have some update regarding low player teams . But couple issues , 1. Tiredness are way too high 2. What about youth development ? It has to be changed as well , because if playing 20-25 mins gives so much tiredness it will affect their development . 3. Market , Sometimes you just can’t afford 9 or more players , the prices have to be recalculated, especially for older people . And for god sakes bring back the function to borrow two players .
--
84 賽季
9 天
--
(翻譯)
(翻譯 EN)
+7
Increasing squad size is a good approach in principle, unfortunately it's just not that easy in the lower leagues to keep many players and remain successful at the same time. The financial strength is simply not there.
This would again favor the big clubs and the smaller ones would be left behind. -- 84 賽季 9 天
This would again favor the big clubs and the smaller ones would be left behind. -- 84 賽季 9 天
--
(翻譯)
(翻譯 EN)
+4
Thank you all for feedback, we are working on this!
As about tiredness:
In the previous system tiredness was hugely dependent on tactics. That leads to situations when:
Even young players can be completely exhausted only after 20 min
Even old players can be not tired at all after 40 minutes
Now tactical impact is significantly reduced and the impact of age/minutes is significantly increased.
The previous version probably is more correct and logic if we talk about “one match”. But as we do not have random injuries and the same scenario can be whole seasons - that leads to the possibility of using only 5 players the whole season.
There might be some more balancing updates regarding tiredness, but not to the level that you can play 35 minutes without making your player tired.
We understand that some of you planned to use national leagues as “training camp” for young players, and this update changes your plan. When we can, we always try to avoid such situations.
National leagues were chosen because it saves a lot of time for us, and that is the resource we really don't have now. Probably we will use the same model in the future as well.
Please use this topic only for your feedback about the match engine.
Currently we do not have time to answer your questions, but at some point of this season we hope to be able to write a bit more about some aspects of this match engine and in which direction we want to go. -- 84 賽季 9 天
As about tiredness:
In the previous system tiredness was hugely dependent on tactics. That leads to situations when:
Even young players can be completely exhausted only after 20 min
Even old players can be not tired at all after 40 minutes
Now tactical impact is significantly reduced and the impact of age/minutes is significantly increased.
The previous version probably is more correct and logic if we talk about “one match”. But as we do not have random injuries and the same scenario can be whole seasons - that leads to the possibility of using only 5 players the whole season.
There might be some more balancing updates regarding tiredness, but not to the level that you can play 35 minutes without making your player tired.
We understand that some of you planned to use national leagues as “training camp” for young players, and this update changes your plan. When we can, we always try to avoid such situations.
National leagues were chosen because it saves a lot of time for us, and that is the resource we really don't have now. Probably we will use the same model in the future as well.
Please use this topic only for your feedback about the match engine.
Currently we do not have time to answer your questions, but at some point of this season we hope to be able to write a bit more about some aspects of this match engine and in which direction we want to go. -- 84 賽季 9 天
--
(翻譯)
(翻譯 EN)
+9
I agree with what you write, just now it seems a bit too much
--
84 賽季
9 天
--
(翻譯)
(翻譯 EN)
+0
tempas lėtas - 27 min, amžius 25, nuovargis 79; min 17, amžius 34, nuovargis 70. 比賽
--
84 賽季
9 天
比賽
--
84 賽季
9 天
--
(翻譯)
(翻譯 EN)
+0
1.1
"Now tactical impact is significantly reduced and the impact of age/minutes is significantly increased. "
Making it less realistic. 36 year old Lebron (almost 37) is easily putting out 40mins per game:
https://www.espn.com/nba/boxscore/_/gameId/401359864
In reality the tiredness was completely fine. NBA playoffs also go with few players and lower leagues in real life usually have very few players playing for them. The issue in real world are only injuries. That's why teams generally have more players. But even there you would find some teams with less players.
And not to mention fast breaks, they are getting increasingly unrealistic. -- 84 賽季 10 天
Making it less realistic. 36 year old Lebron (almost 37) is easily putting out 40mins per game:
https://www.espn.com/nba/boxscore/_/gameId/401359864In reality the tiredness was completely fine. NBA playoffs also go with few players and lower leagues in real life usually have very few players playing for them. The issue in real world are only injuries. That's why teams generally have more players. But even there you would find some teams with less players.
And not to mention fast breaks, they are getting increasingly unrealistic. -- 84 賽季 10 天
--
(翻譯)
(翻譯 EN)
+2
Do not forget, to mention, how real nba players are saving before playoffs :) you know, personaly for me, basketpulse is more similar to futzal basketball, because most of teams has less than 8 players.
--
84 賽季
10 天
--
(翻譯)
(翻譯 EN)
+1
true, but above Lebron's performance is in regular season. Players are generally saving because of risk of injuries.
--
84 賽季
11 天
--
(翻譯)
(翻譯 EN)
+0
Injuries in this game would be interesting update, but then your rate of success would corelate with your luck. It would be more realistic, but it would be unfair for someone.
I Would be happy if injuries were to be determined not only by health but ulso by factor of success -- 84 賽季 11 天
I Would be happy if injuries were to be determined not only by health but ulso by factor of success -- 84 賽季 11 天
--
(翻譯)
(翻譯 EN)
+1
Updated: Version: 2021-10-27-02
Bug fixes:
-3 seconds rule should not be violated too soon
-after turnovers some attacks instantly started in front court
-after 5th foul is received, sometimes substitutions occurred too late.
- sometimes players were a bit tired even without playing time
- wrong player was displayed in chronology events for deflections
-14s instead of 24s after free-throw shots
Balancing:
-a bit reduced influence of offensive rebounds and tight (double) defense towards tiredness.
-a bit reduced amount of traveling cases
-a bit increased amount of events related with tiredness
Many of you do not include match links in your comments.
Please, always include a match link and a few chronology events after the time of the reported occurrence.
On every match page you can find the ME (match engine) version. Please, double check if your example is from the latest ME before posting.
With every update we will try to fix all known bugs. So if some of the bugs repeat - please inform us. When all bugs are fixed - we will switch towards balancing. -- 84 賽季 11 天
Bug fixes:
-3 seconds rule should not be violated too soon
-after turnovers some attacks instantly started in front court
-after 5th foul is received, sometimes substitutions occurred too late.
- sometimes players were a bit tired even without playing time
- wrong player was displayed in chronology events for deflections
-14s instead of 24s after free-throw shots
Balancing:
-a bit reduced influence of offensive rebounds and tight (double) defense towards tiredness.
-a bit reduced amount of traveling cases
-a bit increased amount of events related with tiredness
Many of you do not include match links in your comments.
Please, always include a match link and a few chronology events after the time of the reported occurrence.
On every match page you can find the ME (match engine) version. Please, double check if your example is from the latest ME before posting.
With every update we will try to fix all known bugs. So if some of the bugs repeat - please inform us. When all bugs are fixed - we will switch towards balancing. -- 84 賽季 11 天
--
(翻譯)
(翻譯 EN)
+2
so for tomorrows national league matches, is it the old or the new ME?
--
84 賽季
11 天
--
(翻譯)
(翻譯 EN)
+1
O kodėl negalime gauti tam tikro kiekio nemokamų papildomų rungtynių būsimo varikliuko testams atlikti? Įdiegiant naujoves būtų logiška informuoti kiek įmanoma anksčiau, pateikiant išsamią informaciją kas pasikeis. Dabar Jūsų vartotojai nukenčia, nes buvo prisitaikę prie sistemos, čia strateginis ir ilgalaikis žaidimas, matomai nemaža dalis yra sunerimę. Tai ištikrųjų įtakoja ir rezultatus, žaidėjų būklę ir progresą, kažkam tikriausiai ir finansiškai atsilieps. Siūlyčiau pateikti išsamesnę informaciją apie pakeitimus ir testus perkelti į nemokamas papildomas ryngtynes. Būtų šaunu.
--
84 賽季
11 天
--
(翻譯)
(翻譯 EN)
+9
Has the rate of fast breaks been balanced?
The problems i see with fast breaks is that they don t seem to be dependent on players skills - they simply succeed, no matter if player is good or bad.
Second problem, there should be a way to stop / defend against fast breaks ( if the full court pressure is meant for this, doesn t seem to be working). Every attack should haver an optimal way to defend & and every defense should have amb optimal way to attack. If this is nit well balanced then the tactical richness is ruined. -- 84 賽季 12 天
The problems i see with fast breaks is that they don t seem to be dependent on players skills - they simply succeed, no matter if player is good or bad.
Second problem, there should be a way to stop / defend against fast breaks ( if the full court pressure is meant for this, doesn t seem to be working). Every attack should haver an optimal way to defend & and every defense should have amb optimal way to attack. If this is nit well balanced then the tactical richness is ruined. -- 84 賽季 12 天
--
(翻譯)
(翻譯 EN)
+3
There is a way to stop fast breaks, at least it was before. You have to reduce a chance to get an offensive rebound, then your team will reduce opportunities of fast breaks.
It was the main thing back in a day, i hope it still works. -- 84 賽季 12 天
It was the main thing back in a day, i hope it still works. -- 84 賽季 12 天
--
(翻譯)
(翻譯 EN)
+0
Ye but still i playing WL with 10 and hoping to finish NL with 8, now i have to do trades that i don't need to keep balance 10-9 because otherwise they will get to tired. So basically i burred this season...
--
84 賽季
12 天
--
(翻譯)
(翻譯 EN)
+0
The physical problems are still like this. The players are still more tired than dogs. I don't know what GM wants. The health problems of the old players are also changed by GM. now GM thinks the old players are too powerful and wants to weaken the old players. But when we get used to one thing and follow this rule, GM feels there is a problem and must change it. That's it, over and over again. GM, aren't you bored? I'm bored. Forgive me for my impatience.
--
84 賽季
12 天
--
(翻譯)
(翻譯 EN)
+2
If GM doesn't like old players, I suggest GM force old players to retire at the age of 35. Stop messing around. Yes, we play your game. You have the right to change the rules. We can only adapt to the game. But you should also consider the feelings of our customers. I agree with you on the importance of changing dribbling. You weaken the scout, I can only accept it. If you change your physical strength, I just hope you don't change too much, but now the old players can only play for 10 minutes, I think it's too outrageous.
--
84 賽季
12 天
--
(翻譯)
(翻譯 EN)
+5
Regarding the new engine and GM's indifferent to players, I can only say that I am very disappointed, very disappointed, I will not spend 1 cent for this game, first of all I have stopped renewing my membership.
--
84 賽季
12 天
--
(翻譯)
(翻譯 EN)
+5
The changes are not even final. Admin has clearly stated that the version today is mainly for bug fixes, game balance comes next. They made changes to make the game better, better game earns more money, isn't it that simple?
But I do agree the direction of changes towards tiredness may not be the best. Here is my feedback.
Most of the tactic settings sacrifice tiredness for some other benefits (or vice versa). If effect of tiredness is reduced, the differences between different tactics would be reduced too.
Why can't a player of 40 yrs old stay on the court for 40 mins if they simply stand still all the time? So the problem does not actually come from how long they play, but what they do. Now the defender can create huge pressure to attacker even they have loose defense. Or team can still score too well even they have slow pacing. My 2 cents. -- 84 賽季 12 天
But I do agree the direction of changes towards tiredness may not be the best. Here is my feedback.
Most of the tactic settings sacrifice tiredness for some other benefits (or vice versa). If effect of tiredness is reduced, the differences between different tactics would be reduced too.
Why can't a player of 40 yrs old stay on the court for 40 mins if they simply stand still all the time? So the problem does not actually come from how long they play, but what they do. Now the defender can create huge pressure to attacker even they have loose defense. Or team can still score too well even they have slow pacing. My 2 cents. -- 84 賽季 12 天
--
(翻譯)
(翻譯 EN)
+4
some notices of today's game 比賽
1) best players come to court only at 2:06 before game end
2) is 2vs2 working ok? it said a lot that it was not good situation for shots for my shooters for 2vs2 (Ragauskas, Nekrašius), although i think before such message was given for centers only.
3) Still they shot a lot from under the basket - 16 shots from under the basket from shooters or guards, who should shoot only when necessary (never before such large number. Even in last 2 minutes there were 3 shots from my guards from under basked (setting only necessary), how come a shooter or a guard appears under the basked? also strange as i have much more good situations.
4) from what was the playing time, it might seem that I set to play a lot for young players, but actually most of my older players played ~3-4 minutes less than set, and younger played a bit more. No foul trouble, so difference seems quite big. For example, Maidin set 17min, played only 13.
5) still about tiredness, a) could we agree on the terms when player is tired? I think it is when indicator shows yellow or red and trainings get affected and risk losing form, i.e. from 60%. if some other limit, please then adjust the training side. It would be a lot of work for users to go adjust the trainings % each day.
b) could we agree when player should become tired, for example, on normal tempo, up to 30min player under 30. Up to 25min player above 30. Maybe up to 20min player above 35. If they exceed, maybe automatically they should go to be tired with small adjustment for tempo and fast breaks? Lets discuss, agree or vote! Now my 25-28y still prospect level plays 26min and is almost in the red zone. Set tempo was low and no fast breaks for both teams!
6) look that game would remain balanced lets say if we keep tiredness as bad as it is, maybe then some balancing could be done on the other sides - younger players get same training points for less time played, form adjusted, or if teams are forced to use more players, then decrease min wage (haha- not gona happen :)), but sad to see players being wasted in market. Also if you want to see less 35-40y players, decrease the impact of experience - it is one of the harder skill to accumulate, but is too valuable.
Hope you find it useful -- 84 賽季 13 天
比賽1) best players come to court only at 2:06 before game end
2) is 2vs2 working ok? it said a lot that it was not good situation for shots for my shooters for 2vs2 (Ragauskas, Nekrašius), although i think before such message was given for centers only.
3) Still they shot a lot from under the basket - 16 shots from under the basket from shooters or guards, who should shoot only when necessary (never before such large number. Even in last 2 minutes there were 3 shots from my guards from under basked (setting only necessary), how come a shooter or a guard appears under the basked? also strange as i have much more good situations.
4) from what was the playing time, it might seem that I set to play a lot for young players, but actually most of my older players played ~3-4 minutes less than set, and younger played a bit more. No foul trouble, so difference seems quite big. For example, Maidin set 17min, played only 13.
5) still about tiredness, a) could we agree on the terms when player is tired? I think it is when indicator shows yellow or red and trainings get affected and risk losing form, i.e. from 60%. if some other limit, please then adjust the training side. It would be a lot of work for users to go adjust the trainings % each day.
b) could we agree when player should become tired, for example, on normal tempo, up to 30min player under 30. Up to 25min player above 30. Maybe up to 20min player above 35. If they exceed, maybe automatically they should go to be tired with small adjustment for tempo and fast breaks? Lets discuss, agree or vote! Now my 25-28y still prospect level plays 26min and is almost in the red zone. Set tempo was low and no fast breaks for both teams!
6) look that game would remain balanced lets say if we keep tiredness as bad as it is, maybe then some balancing could be done on the other sides - younger players get same training points for less time played, form adjusted, or if teams are forced to use more players, then decrease min wage (haha- not gona happen :)), but sad to see players being wasted in market. Also if you want to see less 35-40y players, decrease the impact of experience - it is one of the harder skill to accumulate, but is too valuable.
Hope you find it useful -- 84 賽季 13 天
--
(翻譯)
(翻譯 EN)
+13
Updated: Version: 2021-10-31-01
Bug fixes:
- new shot clock after fast break attack
Balancing:
-changes related passing/stealing/turnovers
-when shot clock is getting close to the end, team is trying to give the ball to the leader
-reduced events: quick pass forward with the goal to create fast break opportunity
Other changes:
-usually only perfect passes or passes before the end of attack are visible in chronology. To make it easier to understand what`s happening in the test engine all pases will be visible in chronology.
A bit information how ME works regarding passes/turnovers.
Passing is one of the ways to get players in a good shooting situation. Players who have ability to pass (or have “playmaker” type) are more willing to take risks with passes. A more risky pass can create great opportunities for team members but at the same time it can lead to turnover.
During the match players adapt and for some time after turnovers they tend to do less risky passes to avoid repeating turnover.
Similar system is in other parts. For example drives to the basket. So if player's drives are not working - he stops driving and goes to other options (passing/shooting).
In the new match engine players without good passing skill should not do many turnovers (instead they should use safier passes). -- 84 賽季 14 天
Bug fixes:
- new shot clock after fast break attack
Balancing:
-changes related passing/stealing/turnovers
-when shot clock is getting close to the end, team is trying to give the ball to the leader
-reduced events: quick pass forward with the goal to create fast break opportunity
Other changes:
-usually only perfect passes or passes before the end of attack are visible in chronology. To make it easier to understand what`s happening in the test engine all pases will be visible in chronology.
A bit information how ME works regarding passes/turnovers.
Passing is one of the ways to get players in a good shooting situation. Players who have ability to pass (or have “playmaker” type) are more willing to take risks with passes. A more risky pass can create great opportunities for team members but at the same time it can lead to turnover.
During the match players adapt and for some time after turnovers they tend to do less risky passes to avoid repeating turnover.
Similar system is in other parts. For example drives to the basket. So if player's drives are not working - he stops driving and goes to other options (passing/shooting).
In the new match engine players without good passing skill should not do many turnovers (instead they should use safier passes). -- 84 賽季 14 天
--
(翻譯)
(翻譯 EN)
+6
比賽When you're watching the game live, you can't see "very bad situation". The place where the shot situation should be visible is just blank. When you are watching the chronology after the game ends, you can see "very bad situation". -- 84 賽季 15 天
--
(翻譯)
(翻譯 EN)
+0
Still ...10 players - zone defence , no fast brakes, defend mnostly normal , max player time 23min. Offeence slow, presing - never . And awerage tired 75% .... i dont give shit about NL i just trying to save players health , and put all tactics as slow as posible even i know that i'm going to loose and tirednes is 75. so what i can do more?....
--
84 賽季
15 天
--
(翻譯)
(翻譯 EN)
+6
It would be good to have an explanation about how this new engine is, what you want to achieve, not only to ensure that there is no fatigue, but even to take the shots, for example. It cannot be that the pg and sg shoot short when their strength is triple and they pivot practically or have thrown to the hoop
--
84 賽季
15 天
--
(翻譯)
(翻譯 EN)
+3
Does relaxed defence even working? same minutes, with relaxed defence +20 tiredness.
--
84 賽季
16 天
--
(翻譯)
(翻譯 EN)
+0
2.2 比賽I watched this game live, and there were a couple instances, in the last minute or so, when the clock continued to run (didn't stop) after a basket made, or a foul.
Sorry, I cannot be more specific because the wording of the game report is now completely different from yesterday's live commentary.
For sure, click didn't stop after the last basket.
BTW, the endless sequence of "who passes to who" is utterly messed up!
The players of the 2 teams are mixed, without rhyme or reason :O
They keep passing to each other, all 10 players, on every possession -- 84 賽季 17 天
--
(翻譯)
(翻譯 EN)
+0
Updated: Version: 2021-11-03-01
Bug fixes:
- during LIVE matches situation was not always visible
Balancing:
- still working with balancing passing. Also added possibility of foul during steal attempt.
Other changes:
- if team has only a few seconds for the last attack, it still attempts to move the ball closer and shoot from closer position instead of shooting from the other side of the court -- 84 賽季 17 天
Bug fixes:
- during LIVE matches situation was not always visible
Balancing:
- still working with balancing passing. Also added possibility of foul during steal attempt.
Other changes:
- if team has only a few seconds for the last attack, it still attempts to move the ball closer and shoot from closer position instead of shooting from the other side of the court -- 84 賽季 17 天
--
(翻譯)
(翻譯 EN)
+3
https://www.basketpulse.com/en/League/194/descriptionBut in NL page; we can see the half time scores of the matches... -- 84 賽季 18 天
--
(翻譯)
(翻譯 EN)
+0
+0
比賽In 6 Turkish NL matches, only this match isn't stuck and continues live game... -- 84 賽季 18 天
--
(翻譯)
(翻譯 EN)
+0
Pastrigo rungtynės. 比賽
1 kėlinys liko 05:45
Atvaizdavime pastebėjau bent kelias klaidas : atliekamas pasas priešininko komandos žaidėjams:
K1 06:44 SAKAtliktas nerizikingas perdavimas: R. Páez (→ S. Lund )
K1 06:29 BCGAtliktas nerizikingas perdavimas: A. Žukauskas (→ N. Laucys )
K1 06:17 SAKAtliktas nerizikingas perdavimas: R. Páez (→ L. Vörös ) -- 84 賽季 18 天
比賽1 kėlinys liko 05:45
Atvaizdavime pastebėjau bent kelias klaidas : atliekamas pasas priešininko komandos žaidėjams:
K1 06:44 SAKAtliktas nerizikingas perdavimas: R. Páez (→ S. Lund )
K1 06:29 BCGAtliktas nerizikingas perdavimas: A. Žukauskas (→ N. Laucys )
K1 06:17 SAKAtliktas nerizikingas perdavimas: R. Páez (→ L. Vörös ) -- 84 賽季 18 天
--
(翻譯)
(翻譯 EN)
+1
FAstbreaks always are 2 points. Today I set fastbreaks all the time...0 fastbreaks.
Points after off rebound...0 in the match. 6 steals in total...do not understand anything -- 84 賽季 18 天
Points after off rebound...0 in the match. 6 steals in total...do not understand anything -- 84 賽季 18 天
--
(翻譯)
(翻譯 EN)
+1
比賽1st quater ends with defensive rebound in 9s and shot from the other court in the end -- 84 賽季 18 天
--
(翻譯)
(翻譯 EN)
+0
IMO the game engine is looking much better, the success rate for fast breaks may be a bit too high.
--
84 賽季
18 天
--
(翻譯)
(翻譯 EN)
+5
比賽atlikin4jami nerizikingi perdavimai varžovams
5K 0:01 ŠBS Atliktas nerizikingas perdavimas: R. Gomez ( → P. Dylys) -- 84 賽季 19 天
--
(翻譯)
(翻譯 EN)
+0
Updated: Version: 2021-11-06-01
Bug fixes:
- In match chronology not risky passes were displayed wrongly.
Balancing:
- still working with balancing passes.
- review every place where player defense type is used (tight/loose/double)
- due to some changes in other ME parts, tiredness completely changed and now is a bit rebalanced. However in the final version we still plan to increase it. So keep that in mind for your long-term plans.
We would like to explain a bit how player defense settings will work in the new engine.
In the previous ME the main disadvantage was a bit bigger tiredness. As in the current ME tactics impact on tiredness is significantly reduced, the bigger disadvantage will be visible during the match:
- For tight defense - chances to get foul is increased.
- For double defense - there will be bigger chances to create a good shooting situation for teammates.
- For loose defense chances to get fouled are minimum. -- 84 賽季 20 天
Bug fixes:
- In match chronology not risky passes were displayed wrongly.
Balancing:
- still working with balancing passes.
- review every place where player defense type is used (tight/loose/double)
- due to some changes in other ME parts, tiredness completely changed and now is a bit rebalanced. However in the final version we still plan to increase it. So keep that in mind for your long-term plans.
We would like to explain a bit how player defense settings will work in the new engine.
In the previous ME the main disadvantage was a bit bigger tiredness. As in the current ME tactics impact on tiredness is significantly reduced, the bigger disadvantage will be visible during the match:
- For tight defense - chances to get foul is increased.
- For double defense - there will be bigger chances to create a good shooting situation for teammates.
- For loose defense chances to get fouled are minimum. -- 84 賽季 20 天
--
(翻譯)
(翻譯 EN)
+5
Ramune you say that we must take into account the setting of tactics due to the issue of fatigue, for that we will need teams with more players, so you take into account the renewal of contracts, they are becoming impossible to face, which forces us to reduce teams
--
84 賽季
21 天
--
(翻譯)
(翻譯 EN)
+2
Fast breaks works in unrealistic success percentage. It def has to be fixed. In Lithuania 1 and 2 league games, today it was 38/39.
--
84 賽季
21 天
--
(翻譯)
(翻譯 EN)
+4
I have a small observation. In tactic's review page there is no line about full court press
--
84 賽季
21 天
--
(翻譯)
(翻譯 EN)
+0
+2
Updated: Version: 2021-11-10-01
Bug fixes:
-information about full court press included into tactics review page
Balancing:
- fast-break attacks calibration -- 84 賽季 25 天
Bug fixes:
-information about full court press included into tactics review page
Balancing:
- fast-break attacks calibration -- 84 賽季 25 天
--
(翻譯)
(翻譯 EN)
+3
The event "Three seconds rule violation (in the foul lane):" comes up pretty frequently. Is this intentional. Looks like too much.
--
84 賽季
25 天
--
(翻譯)
(翻譯 EN)
+1
The fastbreaks are still unreal...
14/14 Fast breaks 5/5
比賽
After the successful 3 pointer shot, after 3 seconds a fast break comes... No:1
3:3 1Q 9:04 KSK logotipas 3PT shot: U. Karaman ( Average situation)
Players skills' ratio: 2; Shot quality ratio: 1 Defender: Ş. Çiçek
1Q 9:04 KSK Assist: B. Dinçöz
1Q 9:04 Genc Player speeds to make fast break: Y. Belaçmaz ( Excellent situation)
5:3 1Q 9:01 Genc logotipas Successful fast break: Y. Belaçmaz ( Excellent situation)
Players skills' ratio: 5; Shot quality ratio: 5 Defender: M. Juškėnas
After the successful midrange shot, after 4 seconds a fast break comes... No:2
22:21 1Q 2:07 KSK logotipas Mid-range 2PT shot: S. Yıkılmaz ( Good situation)
Players skills' ratio: 4; Shot quality ratio: 2 Defender: U. Pečinaitis
1Q 2:07 KSK Assist: K. Öz
1Q 2:07 Genc Player speeds to make fast break: N. Tunçeri ( Excellent situation)
24:21 1Q 2:03 Genc logotipas Successful fast break: N. Tunçeri ( Excellent situation)
Players skills' ratio: 3; Shot quality ratio: 5 Defender: M. Juškėnas
After the successful midrange shot, after 4 seconds a fast break comes... No:3
28:31 2Q 7:23 KSK logotipas Mid-range 2PT shot: Q. Yun ( Good situation)
Players skills' ratio: 4; Shot quality ratio: 2 Defender: M. Şanlı
2Q 7:23 Genc Player speeds to make fast break: N. Tunçeri ( Excellent situation)
30:31 2Q 7:19 Genc logotipas Successful fast break: N. Tunçeri ( Excellent situation)
Players skills' ratio: 3; Shot quality ratio: 5 Defender: M. Juškėnas
At the last quarter, the ball comes from the side after a travelling situation, after 4 second a fast break comes!.. No:4
4Q 4:07 KSK logotipas Traveling violation: Q. Yun
4Q 4:07 Genc logotipas Substitution out: N. Tunçeri ( SG)
4Q 4:07 Genc logotipas Substitution out: M. Şanlı ( SF)
4Q 4:07 Genc logotipas Substitution out: S. Bayram ( PF)
4Q 4:07 Genc logotipas Best players are substituted in: U. Pečinaitis ( SG)
4Q 4:07 Genc logotipas Best players are substituted in: Ş. Çiçek ( SF)
4Q 4:07 Genc logotipas Best players are substituted in: O. Sunalp ( PF)
4Q 4:07 KSK logotipas Substitution out: Q. Yun ( SF)
4Q 4:07 KSK logotipas Substitution out: K. Öz ( PF)
4Q 4:07 KSK logotipas Best players are substituted in: S. Yıkılmaz ( SF)
4Q 4:07 KSK logotipas Best players are substituted in: Q. Yun ( PF)
4Q 4:07 Genc Player speeds to make fast break: Y. Belaçmaz ( Excellent situation)
67:58 4Q 4:03 Genc logotipas Successful fast break: Y. Belaçmaz ( Excellent situation)
Players skills' ratio: 2; Shot quality ratio: 5 Defender: H. Conde
At last 32 seconds after a successful midrange shot, after 4 seconds a fastbreak comes... No:5
76:68 4Q 0:32 KSK logotipas Mid-range 2PT shot: S. Yıkılmaz ( Average situation)
Players skills' ratio: 4; Shot quality ratio: 1 Defender: U. Pečinaitis
4Q 0:32 Genc Player speeds to make fast break: Y. Belaçmaz ( Excellent situation)
78:68 4Q 0:28 Genc logotipas Successful fast break: Y. Belaçmaz ( Excellent situation)
Players skills' ratio: 5; Shot quality ratio: 5 Defender: T. Erbakan
I didn't write the fast breaks after rebounds and steals, there are 14 more fastbreaks after steals and rebounds all are successful, but the ones that are upside looks unreal and not logical, and the tirednesses that are making those fastbreaks looks unreal and not logical too; it must be considered and balanced again I suppose... Success rate also must be balanced again... -- 84 賽季 25 天
14/14 Fast breaks 5/5
比賽After the successful 3 pointer shot, after 3 seconds a fast break comes... No:1
3:3 1Q 9:04 KSK logotipas 3PT shot: U. Karaman ( Average situation)
Players skills' ratio: 2; Shot quality ratio: 1 Defender: Ş. Çiçek
1Q 9:04 KSK Assist: B. Dinçöz
1Q 9:04 Genc Player speeds to make fast break: Y. Belaçmaz ( Excellent situation)
5:3 1Q 9:01 Genc logotipas Successful fast break: Y. Belaçmaz ( Excellent situation)
Players skills' ratio: 5; Shot quality ratio: 5 Defender: M. Juškėnas
After the successful midrange shot, after 4 seconds a fast break comes... No:2
22:21 1Q 2:07 KSK logotipas Mid-range 2PT shot: S. Yıkılmaz ( Good situation)
Players skills' ratio: 4; Shot quality ratio: 2 Defender: U. Pečinaitis
1Q 2:07 KSK Assist: K. Öz
1Q 2:07 Genc Player speeds to make fast break: N. Tunçeri ( Excellent situation)
24:21 1Q 2:03 Genc logotipas Successful fast break: N. Tunçeri ( Excellent situation)
Players skills' ratio: 3; Shot quality ratio: 5 Defender: M. Juškėnas
After the successful midrange shot, after 4 seconds a fast break comes... No:3
28:31 2Q 7:23 KSK logotipas Mid-range 2PT shot: Q. Yun ( Good situation)
Players skills' ratio: 4; Shot quality ratio: 2 Defender: M. Şanlı
2Q 7:23 Genc Player speeds to make fast break: N. Tunçeri ( Excellent situation)
30:31 2Q 7:19 Genc logotipas Successful fast break: N. Tunçeri ( Excellent situation)
Players skills' ratio: 3; Shot quality ratio: 5 Defender: M. Juškėnas
At the last quarter, the ball comes from the side after a travelling situation, after 4 second a fast break comes!.. No:4
4Q 4:07 KSK logotipas Traveling violation: Q. Yun
4Q 4:07 Genc logotipas Substitution out: N. Tunçeri ( SG)
4Q 4:07 Genc logotipas Substitution out: M. Şanlı ( SF)
4Q 4:07 Genc logotipas Substitution out: S. Bayram ( PF)
4Q 4:07 Genc logotipas Best players are substituted in: U. Pečinaitis ( SG)
4Q 4:07 Genc logotipas Best players are substituted in: Ş. Çiçek ( SF)
4Q 4:07 Genc logotipas Best players are substituted in: O. Sunalp ( PF)
4Q 4:07 KSK logotipas Substitution out: Q. Yun ( SF)
4Q 4:07 KSK logotipas Substitution out: K. Öz ( PF)
4Q 4:07 KSK logotipas Best players are substituted in: S. Yıkılmaz ( SF)
4Q 4:07 KSK logotipas Best players are substituted in: Q. Yun ( PF)
4Q 4:07 Genc Player speeds to make fast break: Y. Belaçmaz ( Excellent situation)
67:58 4Q 4:03 Genc logotipas Successful fast break: Y. Belaçmaz ( Excellent situation)
Players skills' ratio: 2; Shot quality ratio: 5 Defender: H. Conde
At last 32 seconds after a successful midrange shot, after 4 seconds a fastbreak comes... No:5
76:68 4Q 0:32 KSK logotipas Mid-range 2PT shot: S. Yıkılmaz ( Average situation)
Players skills' ratio: 4; Shot quality ratio: 1 Defender: U. Pečinaitis
4Q 0:32 Genc Player speeds to make fast break: Y. Belaçmaz ( Excellent situation)
78:68 4Q 0:28 Genc logotipas Successful fast break: Y. Belaçmaz ( Excellent situation)
Players skills' ratio: 5; Shot quality ratio: 5 Defender: T. Erbakan
I didn't write the fast breaks after rebounds and steals, there are 14 more fastbreaks after steals and rebounds all are successful, but the ones that are upside looks unreal and not logical, and the tirednesses that are making those fastbreaks looks unreal and not logical too; it must be considered and balanced again I suppose... Success rate also must be balanced again... -- 84 賽季 25 天
--
(翻譯)
(翻譯 EN)
+2
The fast break attempts and success rate of other matches in Turkish national league..
比賽
4/4 Fast breaks 6/6
10/10 success rate
比賽
0/0 Fast breaks 0/0
No fast break attempts; strange...
比賽
0/0 Fast breaks 17/17
17/17 success rate by only one team, strange...
比賽
9/12 Fast breaks 1/1
10/13 success rate...
比賽
0/0 Fast breaks 4/4
4/4 success rate..
So in 6 matches, only one team missed 3 fast break shots in 12 attempts, the other 60 fast break shots are successful, it is %95 (60/63)
And fast break attempts variance is very high; 0 4 10 13 17 19 in 6 matches
0 0 0 1 4 4 5 6 10 12 14 17 in 12 teams
It has to be looked over and balanced again I suppose... -- 84 賽季 25 天
比賽4/4 Fast breaks 6/6
10/10 success rate
比賽0/0 Fast breaks 0/0
No fast break attempts; strange...
比賽0/0 Fast breaks 17/17
17/17 success rate by only one team, strange...
比賽9/12 Fast breaks 1/1
10/13 success rate...
比賽0/0 Fast breaks 4/4
4/4 success rate..
So in 6 matches, only one team missed 3 fast break shots in 12 attempts, the other 60 fast break shots are successful, it is %95 (60/63)
And fast break attempts variance is very high; 0 4 10 13 17 19 in 6 matches
0 0 0 1 4 4 5 6 10 12 14 17 in 12 teams
It has to be looked over and balanced again I suppose... -- 84 賽季 25 天
--
(翻譯)
(翻譯 EN)
+2
Correction: 0 0 0 0 1 4 4 5 6 12 14 17 in 12 teams
Success rate of double digit fast break attempts should be lowered... -- 84 賽季 25 天
Success rate of double digit fast break attempts should be lowered... -- 84 賽季 25 天
--
(翻譯)
(翻譯 EN)
+2
Every time they want to fix something they make it worse. Better not touch anything
--
84 賽季
25 天
--
(翻譯)
(翻譯 EN)
+2
Updated: Version: 2021-11-13-01
Balancing:
- fast-break attacks calibration
A bit of information on how fast-break is supposed to work.
In the new match engine fast-break usually starts in two ways:
1. With a good pass soon after rebound. Usually starts when the player who rebounded the ball has good passing/IQ skills. Such fast-breaks can be significantly reduced by the opposing team if they do not fight for offensive rebounds.
2. After a steal. Usually starts when the player who stole the ball has good dribbling and speed. Such a fast-break highly depends on how many steals the team makes.
Fast breaks in excellent situations almost always will end successfully, it is quite similar to real basketball.
In the other situations it will also depend on the closest defender’s skills.
So if a team uses tactical setting “rarely”, it can expect to have little fast-breaks but with a percentage close to 100%.
--------------------------
Also we would like to update information about when we expect to have the match engine in all games. As we still have a lot of work, we probably won't finish balancing everything until the end of this season. So we expect that the match engine will be used in all leagues not earlier than 87th season. -- 84 賽季 27 天
Balancing:
- fast-break attacks calibration
A bit of information on how fast-break is supposed to work.
In the new match engine fast-break usually starts in two ways:
1. With a good pass soon after rebound. Usually starts when the player who rebounded the ball has good passing/IQ skills. Such fast-breaks can be significantly reduced by the opposing team if they do not fight for offensive rebounds.
2. After a steal. Usually starts when the player who stole the ball has good dribbling and speed. Such a fast-break highly depends on how many steals the team makes.
Fast breaks in excellent situations almost always will end successfully, it is quite similar to real basketball.
In the other situations it will also depend on the closest defender’s skills.
So if a team uses tactical setting “rarely”, it can expect to have little fast-breaks but with a percentage close to 100%.
--------------------------
Also we would like to update information about when we expect to have the match engine in all games. As we still have a lot of work, we probably won't finish balancing everything until the end of this season. So we expect that the match engine will be used in all leagues not earlier than 87th season. -- 84 賽季 27 天
--
(翻譯)
(翻譯 EN)
+6
I looked at all Türkish National League matches fast break numbers, as I see, fast break calibration worked good, In our match, all fast break attempts came after rebounds or steals, so balancing worked I think, thanks...
--
84 賽季
28 天
--
(翻譯)
(翻譯 EN)
+0
比賽Please look at the score. It's too low. And a single quarter score of 2-1. This is not normal. -- 84 賽季 29 天
--
(翻譯)
(翻譯 EN)
+3
Overall, I like the way the new GE is being tweaked, it seems mostly to get better each week.
--
84 賽季
30 天
--
(翻譯)
(翻譯 EN)
+5
Kelios pastabos dėl greitų atakų suprantu kad pasibaigęs laikas ir pražanga puolime yra priskiriama prie klaidų ir po klaidų greitų atakų reikšmė yra padidinta, bet šiaip šios dvi klaidos dažniausiai neturi įtakos žaidėjų grįžimui į ginybą nes kamuolys išsimetamas iš už galo, tad labai keista kai po jų greitos atakos veikia taip pat kaip po perimto kamuolio. Taip pat labai keistai atrodo kai rezgama ataka , prasižengia besiginanti komanda ir turi 14 naujų sekundžių ir komanda surengia greitą ataką.... kas iš principo yra neįmanoma.
--
84 賽季
31 天
--
(翻譯)
(翻譯 EN)
+1
比賽 0/5 Fast breaks - vidutinis nustatymas prieš 2WL klubą ir visos nesėkmingos atakos baigėsi taip:
1Q 2:38 BULL Player speeds to make fast break: N. Di ( Excellent situation)
1Q 2:34 BULL logotipas Fast break ended with turnover: N. Di
Žaidėjas turi greitį, turi varymasį, turi patirtį, turi kitus įgūdžius. -- 84 賽季 31 天
--
(翻譯)
(翻譯 EN)
+0
I had FB set to highest possible, not sure about Mario... went 0/0 and my PG who excels at assisting took 11 shots, making 0. This seems off. 比賽
--
84 賽季
31 天
比賽
--
84 賽季
31 天
--
(翻譯)
(翻譯 EN)
+0
I looked at 6 Turkish league match stats at day 31; fast break numbers are more normal as I see, but I saw another strange stats; number of blocks are slightly decreased as I see; 0 0 0 1 1 2 ; total number of blocks in 6 matches is only 4, so average number of blocks per match is only 0.67 and average number of blocks per team is only 0,33, it is not logic and there is a problem I suppose; 0 0 0 0 0 0 0 0 1 1 1 1; 8 teams couldn't block any shot, 4 teams could block 1 shot only in whole match, it is not near a possible statistic I suppose...
比賽
比賽
比賽
比賽
比賽
比賽
--
84 賽季
32 天
比賽 比賽 比賽 比賽 比賽 比賽
--
84 賽季
32 天
--
(翻譯)
(翻譯 EN)
+1
When the difference in quality of the two teams is really big it used to be that there came a point as the leading team "slows down". It seems that this is not the case anymore.
I had this Impression in the last two NL Matches.
Is this effect intentional? -- 84 賽季 34 天
I had this Impression in the last two NL Matches.
Is this effect intentional? -- 84 賽季 34 天
--
(翻譯)
(翻譯 EN)
+0
Updated: Version: 2021-11-22-01
Bug fixes:
- some fast-breaks occurred due to full-court press and that was not visible in chronology. Now a full court press event will appear before starting the attack.
- fixed situations when in 8 seconds a team does not manage to advance to the frontcourt.
Balancing:
- reduced chances to have low-scoring matches.
- increased relaxation factor when one team leads by huge difference. -- 84 賽季 37 天
Bug fixes:
- some fast-breaks occurred due to full-court press and that was not visible in chronology. Now a full court press event will appear before starting the attack.
- fixed situations when in 8 seconds a team does not manage to advance to the frontcourt.
Balancing:
- reduced chances to have low-scoring matches.
- increased relaxation factor when one team leads by huge difference. -- 84 賽季 37 天
--
(翻譯)
(翻譯 EN)
+7
I set fast breaks to often and I believe that is the reason why every player on my team hit 100% tiredness. I get that, but they took a total of 9 fast breaks. Shouldn't the number of fast breaks be correlated with the player tiredness, not just tactic setting?
--
84 賽季
37 天
--
(翻譯)
(翻譯 EN)
+0
Updated: Version: 2021-11-25-01
Bug fixes:
- sometimes in set plays the situation was created for the player that is not supposed to shoot from that place based on tactical settings.
Balancing:
- increased chances to miss shots from medium/three point range (even when there is a good/excellent attack situation).
- a bit increased amount of set plays. Also made some additional balancing updates here (bigger coach’s impact, reduced player defensive tactics’ impact)
- balancing of driving to the basket. Smaller players will have more chances to create better situations while driving against bigger/slower defenders. Also increased chances to commit a foul with tight defence when the opponent is driving.
Also we would like to explain a bit more about players’ situations and in which direction we are going.
One of the most important things in the new match engine is to create good shooting situations or to find mismatches.
Players that can do many things (for example, shoot from different ranges) should be able to create good situations a bit easier compared to players that can do only one thing on the court.
We hope that with time players (especially with good IQ skills) will become smarter and will choose the right decision based on the opponent. For example, if you are defending a sniper who never does drives - he should be guarded from closer distance. -- 84 賽季 40 天
Bug fixes:
- sometimes in set plays the situation was created for the player that is not supposed to shoot from that place based on tactical settings.
Balancing:
- increased chances to miss shots from medium/three point range (even when there is a good/excellent attack situation).
- a bit increased amount of set plays. Also made some additional balancing updates here (bigger coach’s impact, reduced player defensive tactics’ impact)
- balancing of driving to the basket. Smaller players will have more chances to create better situations while driving against bigger/slower defenders. Also increased chances to commit a foul with tight defence when the opponent is driving.
Also we would like to explain a bit more about players’ situations and in which direction we are going.
One of the most important things in the new match engine is to create good shooting situations or to find mismatches.
Players that can do many things (for example, shoot from different ranges) should be able to create good situations a bit easier compared to players that can do only one thing on the court.
We hope that with time players (especially with good IQ skills) will become smarter and will choose the right decision based on the opponent. For example, if you are defending a sniper who never does drives - he should be guarded from closer distance. -- 84 賽季 40 天
--
(翻譯)
(翻譯 EN)
+3
Few observations:
Significantly reduced steal effect, will this skill become useless? Brings disbalance to training skills.
Minute distribution is very bad. I've been playing with this and it could go as far as +8 minutes, and as low as -6minutes.
Too many shots from PG, especially the ones who are not shooters, double checked they were not made at the last second, even if the clock is ticking, and you have given someone a role of 1. leader 2. shooter 3. aggressive dribbler the ball should be in their hand or/and lastly could stay in hands of the PG. -- 84 賽季 40 天
Significantly reduced steal effect, will this skill become useless? Brings disbalance to training skills.
Minute distribution is very bad. I've been playing with this and it could go as far as +8 minutes, and as low as -6minutes.
Too many shots from PG, especially the ones who are not shooters, double checked they were not made at the last second, even if the clock is ticking, and you have given someone a role of 1. leader 2. shooter 3. aggressive dribbler the ball should be in their hand or/and lastly could stay in hands of the PG. -- 84 賽季 40 天
--
(翻譯)
(翻譯 EN)
+2
比賽Team offence: on big men, but somehow my PG/SG made more shots from close range, than PF/C, how team offence works ? -- 84 賽季 40 天
--
(翻譯)
(翻譯 EN)
+1
比賽Aikštelėje atsarginis pf kurio antra pozicija sf tuo tarpu sf keičia startinis pf kurio antra pozicija c o trečia pozicija sf . Logiškai turėtų susikeisti pozicijom ir startinis pf pasislinkt i pf , o atsarginis pf persislinkt i sf , nes ši yra jo antroji pozicija , o į aikštę išėjusio žaidėjo trečioji. Be taip neįvyksta. + startinis pg žaidžia 12 min be keitimo kai tikrai yra kam keisti .... -- 84 賽季 45 天
--
(翻譯)
(翻譯 EN)
+0
比賽Neveikia atsipalaidavusi gynyba arba nesubalansuotai provokuoja pražangas prasiveržimai. Išsibaudavo žaidėjas per 10 minučių, 5 prasiveržimai - 5 pražangos. Gynyba atsipalaidavusi. Gavo baudas prieš ženkliai blogesnio tvirtumo žaidėją, bei mažesnės patirties, o driblingo įgūdis vidutinis. -- 84 賽季 45 天
--
(翻譯)
(翻譯 EN)
+0
Visas naujas nacionalinės lygos varikliukas kažkokia betvakė, pražangų renkasi neadekvačiai ir nelogiškose situacijose ypač 1-2 kėlinių laikotarpiu. Taip pat toks jausmas, kad rungtynių metu visiškai neatsižvelgiama į taktiką tiek žaidimo laiko prasme, tiek keitimais ar komandine taktika.
--
84 賽季
45 天
--
(翻譯)
(翻譯 EN)
+0
Ant naujo variklio kai pralaiminėjama 3 taškais paskutinėm sekundėm neieškomas tritaškis
--
84 賽季
45 天
--
(翻譯)
(翻譯 EN)
+0
Updated: Version: 2021-12-01-01
Bug fix:
- too big tiredness related to full court press and the effect only for one team. -- 84 賽季 45 天
Bug fix:
- too big tiredness related to full court press and the effect only for one team. -- 84 賽季 45 天
--
(翻譯)
(翻譯 EN)
+4
Per daug prazangu pirmame ketvirtyje, kaikurie žaidėjai gauna po 4 pražangas pirmame kėlinyje o kitus tris visai neprasizengia bet atvirkščiai, fiksuojama priešininkui nors žaidžia po 30 ir daugiau minučių.
Kaip tai suprasti? - Žaidėjas yra geroje pozicijoje atlikti taktinę pražangą, tačiau negali, nes nebus kas jį pakeistų. Čia tai tikra nesąmonė, nes yra antras PG ir dar du atsarginiai kurie antroje pozicijoje gali žaisti PG ir komandoje nėra žaidėjų su 5 pražangomis. -- 84 賽季 46 天
Kaip tai suprasti? - Žaidėjas yra geroje pozicijoje atlikti taktinę pražangą, tačiau negali, nes nebus kas jį pakeistų. Čia tai tikra nesąmonė, nes yra antras PG ir dar du atsarginiai kurie antroje pozicijoje gali žaisti PG ir komandoje nėra žaidėjų su 5 pražangomis. -- 84 賽季 46 天
--
(翻譯)
(翻譯 EN)
+3
比賽After a basket, without a fastbreak, 1 or 2 seconds later, shots to other basket occurs, this is definitely a bug...
Event No:1
0:9 1Q 5:21 GBC logotipas Free throw: D. Soyturk
0:10 1Q 5:21 GBC logotipas Free throw: D. Soyturk
1Q 5:21 GBC logotipas Substitution out: D. Soyturk ( SG)
1Q 5:21 GBC logotipas Substitution in: G. Beyaz ( SG)
1Q 5:20 KSK Excellent pass: M. Juškėnas ( → U. Karaman)
2:10 1Q 5:19 KSK logotipas Close range 2PT shot: U. Karaman ( Average situation)
Players skills' ratio: -4; Shot quality ratio: 2 Defender: D. Tunaitis
Event No:2
17:29 2Q 4:40 GBC logotipas Free throw: M. Narazaki
2Q 4:39 KSK Fine pass: T. Erbakan ( → S. Yıkılmaz)
2Q 4:36 KSK Not risky pass: S. Yıkılmaz ( → Q. Yun)
19:29 2Q 4:35 KSK logotipas Close range 2PT shot: Q. Yun ( Average situation)
Players skills' ratio: 4; Shot quality ratio: 3 Defender: M. Narazaki
Event No:3
34:50 3Q 3:22 KSK logotipas Free throw: Ç. Şahan
3Q 3:21 GBC Not risky pass: R. Xing ( → G. Beyaz)
3Q 3:18 GBC Not risky pass: G. Beyaz ( → M. Narazaki)
34:52 3Q 3:17 GBC logotipas Dunk: M. Narazaki ( Average situation)
Players skills' ratio: 5; Shot quality ratio: -2 Defender: Ç. Şahan
3Q 3:17 GBC Assist: G. Beyaz
Event No:4
46:70 4Q 4:33 GBC logotipas Free throw: D. Soyturk
46:71 4Q 4:33 GBC logotipas Free throw: D. Soyturk
4Q 4:33 KSK logotipas Substitution out: S. Yıkılmaz ( SF)
4Q 4:33 KSK logotipas Substitution in: U. Karaman ( SF)
4Q 4:33 KSK logotipas Substitution out: M. Juškėnas ( C)
4Q 4:33 KSK logotipas Substitution in: K. Öz ( C)
4Q 4:33 KSK logotipas Substitution out: T. Erbakan ( PG)
4Q 4:33 KSK logotipas Substitution in: H. Conde ( PG)
4Q 4:33 GBC logotipas Substitution out: B. Topuz ( SF)
4Q 4:33 GBC logotipas Substitution in: M. İnanç ( SF)
4Q 4:33 GBC logotipas Substitution out: G. Karim ( C)
4Q 4:33 GBC logotipas Substitution in: M. Narazaki ( C)
4Q 4:33 GBC logotipas Substitution out: D. Soyturk ( SG)
4Q 4:33 GBC logotipas Substitution in: G. Beyaz ( SG)
4Q 4:32 KSK Not risky pass: H. Conde ( → A. Mansur)
4Q 4:31 KSK Unlucky 3PT shot: A. Mansur ( Average situation)
Players skills' ratio: -1; Shot quality ratio: 3 Defender: O. Ek
At the beginning of 3rd quarter a fast break occurs, this is another bug...
Quarter: 3
3Q 10:00 KSK Start of the period
3Q 10:00 KSK logotipas Starting point guard: H. Conde ( PG)
3Q 10:00 KSK logotipas Starting shooting guard: U. Karaman ( SG)
3Q 10:00 KSK logotipas Starting small forward: S. Yıkılmaz ( SF)
3Q 10:00 KSK logotipas Starting power forward: Q. Yun ( PF)
3Q 10:00 KSK logotipas Starting center: B. Dinçöz ( C)
3Q 10:00 GBC logotipas Starting point guard: R. Xing ( PG)
3Q 10:00 GBC logotipas Starting shooting guard: D. Soyturk ( SG)
3Q 10:00 GBC logotipas Starting small forward: B. Topuz ( SF)
3Q 10:00 GBC logotipas Starting power forward: D. Tunaitis ( PF)
3Q 10:00 GBC logotipas Starting center: G. Karim ( C)
3Q 10:00 KSK Team in defense is using full court press
3Q 10:00 GBC Player speeds to make fast break: R. Xing ( Excellent situation)
21:42 3Q 9:57 GBC logotipas Successful fast break: R. Xing ( Excellent situation)
Players skills' ratio: -2; Shot quality ratio: 5 Defender: H. Conde
Hope both bugs will be solved again... -- 84 賽季 47 天
--
(翻譯)
(翻譯 EN)
+0
Pabaigoje keistai kažkaip gavosi, kad žaidėjas, kuris turinatlikti taktinę pražangą, negali prasižengti, nes nebus kas jį pakeistų, nors tas žaidėjas turi 1 pražangą, o visa komanda, iš viso prasižengusi 3 kartus per visas rungtynes. Pačios paskutinės 4kėlinio sekundės. Pažiūrėkite, ar ne bugas
--
84 賽季
47 天
--
(翻譯)
(翻譯 EN)
+0
比賽As no correction and adjustment made, early attacks without fastbreaks after successful shots continue unfortunately; it should be corrected and adjusted...
Event No:1
6:5 1Q 7:27 KSK logotipas Free throw: U. Karaman
6:6 1Q 7:27 KSK logotipas Free throw: U. Karaman
1Q 7:26 5IVE Excellent pass: T. Toprak ( → N. Bubelis)
1Q 7:25 5IVE Player is going to make a drive: N. Bubelis
1Q 7:25 KSK Shooting foul (1 f ): U. Karaman
1Q 7:25 5IVE Foul against: N. Bubelis
7:6 1Q 7:25 5IVE logotipas Free throw: N. Bubelis
8:6 1Q 7:25 5IVE logotipas Free throw: N. Bubelis
1Q 7:25 5IVE Free throw missed: N. Bubelis
1Q 7:23 KSK Foul when fighting for rebound (1 f ): K. Öz
1Q 7:23 5IVE Foul against: T. Karaman
9:6 1Q 7:23 5IVE logotipas Free throw: T. Karaman
1Q 7:23 5IVE Free throw missed: T. Karaman
1Q 7:21 KSK Defensive rebound: K. Öz (Nearest opponent: J. Kohlrausch)
Event No:2
17:14 1Q 4:41 KSK logotipas Close range 2PT shot: U. Karaman ( Average situation)
Players skills' ratio: 2; Shot quality ratio: -1 Defender: C. Ha
1Q 4:41 KSK Assist: T. Erbakan
1Q 4:41 5IVE Shooting foul (1 f ): C. Ha
1Q 4:41 KSK Foul against: U. Karaman
17:15 1Q 4:41 KSK logotipas Free throw: U. Karaman
1Q 4:41 KSK logotipas Substitution out due to fouls (saving for end): U. Karaman ( SF)
1Q 4:41 KSK logotipas Substitution in: S. Yıkılmaz ( SF)
1Q 4:40 5IVE Excellent pass: G. Can ( → N. Bubelis)
20:15 1Q 4:39 5IVE logotipas 3PT shot: N. Bubelis ( Bad situation)
Players skills' ratio: 5; Shot quality ratio: 0 Defender: A. Mansur
1Q 4:39 5IVE Assist: G. Can
Event No:3
2Q 2:45 5IVE Shooting foul (2 f ): R. Calderón
2Q 2:45 KSK Foul against: Q. Yun
2Q 2:45 KSK Free throw missed: Q. Yun
45:31 2Q 2:45 KSK logotipas Free throw: Q. Yun
2Q 2:45 5IVE logotipas Substitution out: R. Calderón ( PF)
2Q 2:45 5IVE logotipas Substitution in: T. Karaman ( PF)
2Q 2:45 5IVE logotipas Substitution out: T. Toprak ( PG)
2Q 2:45 5IVE logotipas Substitution in: N. Bubelis ( PG)
2Q 2:45 5IVE logotipas Player is shifted to different position: J. Kohlrausch ( PF)
2Q 2:45 5IVE logotipas Player is shifted to different position: T. Karaman ( C)
2Q 2:44 5IVE Bad pass: N. Bubelis ( → A. Karnisovas)
2Q 2:41 5IVE Average pass: A. Karnisovas ( → N. Bubelis)
2Q 2:40 5IVE Player is going to make a drive: N. Bubelis
2Q 2:40 KSK Defensive foul during a drive to the basket (4 f ): M. Juškėnas
2Q 2:40 5IVE Foul against: N. Bubelis
46:31 2Q 2:40 5IVE logotipas Free throw: N. Bubelis
47:31 2Q 2:40 5IVE logotipas Free throw: N. Bubelis
Hope it will be corrected and adjusted in the next update... -- 84 賽季 53 天
--
(翻譯)
(翻譯 EN)
+0
Pozicijos neveikia aikštelėj žaidėjas kurio pirma pozicija c žaidžia kaip
kaip pf. C žaidžiantį žaidėją keičia žaidėjas kurio pozicija sf o trečią pozicija c ir jis lieka žaisti c. O tikras c lošia kaip pf. Taupomi žaidėjai 3 kėlinio galas trys pražangos. Ir vis dar taupomi. Maža rotacija su antra pozicija nustatyta. Žaidžiant tritaškiais stipriai per mažais tritaškių išmetama, -- 84 賽季 53 天
kaip pf. C žaidžiantį žaidėją keičia žaidėjas kurio pozicija sf o trečią pozicija c ir jis lieka žaisti c. O tikras c lošia kaip pf. Taupomi žaidėjai 3 kėlinio galas trys pražangos. Ir vis dar taupomi. Maža rotacija su antra pozicija nustatyta. Žaidžiant tritaškiais stipriai per mažais tritaškių išmetama, -- 84 賽季 53 天
--
(翻譯)
(翻譯 EN)
+0
比賽K. Pabarčius:
Having 7 times 3 second violation is totally nonsense -- 84 賽季 55 天
--
(翻譯)
(翻譯 EN)
+0
Updated: Version: 2021-12-11-01
Bug fix:
-players with role “important” will be able to make tactical foul in the end of the match (in previous version this event was triggered: Player is in good position to commit a tactical foul but can not because there is no one to substitute him
-after an accurate free-throw, the team immediately started playing near the frontcourt.
Alphan: Thank you for your detailed feedback!
With the fast-break attack in the beginning of the court it is not the bug, full court press gave that opportunity.
One more time we want to remind other users: please, for every feedback - provide a link to the match and the related fragment from Play-by-play. Thank you for your understanding! -- 84 賽季 55 天
Bug fix:
-players with role “important” will be able to make tactical foul in the end of the match (in previous version this event was triggered: Player is in good position to commit a tactical foul but can not because there is no one to substitute him
-after an accurate free-throw, the team immediately started playing near the frontcourt.
Alphan: Thank you for your detailed feedback! With the fast-break attack in the beginning of the court it is not the bug, full court press gave that opportunity.
One more time we want to remind other users: please, for every feedback - provide a link to the match and the related fragment from Play-by-play. Thank you for your understanding! -- 84 賽季 55 天
--
(翻譯)
(翻譯 EN)
+2
na poziciju paskirstymas tai tragiškai veikia. ir 5 bauda.... ner prasmės taupyt žaidėjus dėt nes penktos vis tike nebus ...
--
84 賽季
55 天
--
(翻譯)
(翻譯 EN)
+0
a-ramune : Not at all, but there is a misunderstanding; the events I wrote is not fast breaks or full court press trials, they are 1-5 second attacks after successful shots without a fast break or full court press trials, so they must be solved, at todays match it didn't occur, hope it will not occur in next season's national matches...
--
84 賽季
55 天
--
(翻譯)
(翻譯 EN)
+0
No entiendo que cada vez que se cambia algo siempre hay vencedores y vencidos.
Tema salarios y renovaciones......
Motor de juego nuevo ......
No entiendo la necesidad de reventar el físico de los jugadores.
No se podría hacer algo lógico.
Jugadores de más de 35 años que jueguen más de 16 minutos penalización gorda de físico y al tercer partido lesionado.
De 30 a 35, lo mismo si juegan más de 20 o 24 minutos.
Hasta 30 años ,si juegan mas de 30 minutos, lo mismo.
No se, es una idea. -- 84 賽季 56 天
Tema salarios y renovaciones......
Motor de juego nuevo ......
No entiendo la necesidad de reventar el físico de los jugadores.
No se podría hacer algo lógico.
Jugadores de más de 35 años que jueguen más de 16 minutos penalización gorda de físico y al tercer partido lesionado.
De 30 a 35, lo mismo si juegan más de 20 o 24 minutos.
Hasta 30 años ,si juegan mas de 30 minutos, lo mismo.
No se, es una idea. -- 84 賽季 56 天
--
(翻譯)
(翻譯 EN)
+3
Si Petrovic pero para eso habria que tener la posibilidad de conformar planteles más largos y con el tema de las renovaciones que aumentan mucho los salarios se hace imposible
--
84 賽季
56 天
--
(翻譯)
(翻譯 EN)
+2
Por eso digo que cada vez que se toca algo hace el juego más cuesta arriba
Las renovaciones son subreales y totalmente incomprensibles,no se pueden mantener.
Lo del draft con jugadores sin físico, con habilidades inútiles....... No lo entiendo.
Ahora el motor de juego, totalmente incomprensible lo del físico.
En fin, no voy a entrar en sí son cambios mejores o peores para el juego, pero cada vez desaparecen más equipos y la línea entre seguir en el juego o dejarlo empieza a ser muy fina porque da la sensación de que todos los cambios son para que la gente compre créditos, bien para ver skills de jugadores del draft o para comprar dinero del juego, que yo lo he tenido que hacer esta temporada y no creo que este sea el camino y la línea empieza a ser muy fina.
En fin, es mi opinión y cada uno tiene la suya, pero me da que el camino que se lleva cogiendo de 4 o 5 temporadas para acá no es el adecuado. -- 84 賽季 56 天
Las renovaciones son subreales y totalmente incomprensibles,no se pueden mantener.
Lo del draft con jugadores sin físico, con habilidades inútiles....... No lo entiendo.
Ahora el motor de juego, totalmente incomprensible lo del físico.
En fin, no voy a entrar en sí son cambios mejores o peores para el juego, pero cada vez desaparecen más equipos y la línea entre seguir en el juego o dejarlo empieza a ser muy fina porque da la sensación de que todos los cambios son para que la gente compre créditos, bien para ver skills de jugadores del draft o para comprar dinero del juego, que yo lo he tenido que hacer esta temporada y no creo que este sea el camino y la línea empieza a ser muy fina.
En fin, es mi opinión y cada uno tiene la suya, pero me da que el camino que se lleva cogiendo de 4 o 5 temporadas para acá no es el adecuado. -- 84 賽季 56 天
--
(翻譯)
(翻譯 EN)
+8
Updated: Version: 2021-12-12-01
Balancing:
- slightly reduced amount of three second violations and added a maximum limit for a player (max two times in one match) -- 84 賽季 56 天
Balancing:
- slightly reduced amount of three second violations and added a maximum limit for a player (max two times in one match) -- 84 賽季 56 天
--
(翻譯)
(翻譯 EN)
+1
Version: 2021-12-13-01
In this version, as I mentioned before; amount of blocked shots are slightly reduced as I see; it should be balanced again I think… -- 85 賽季 8 天
In this version, as I mentioned before; amount of blocked shots are slightly reduced as I see; it should be balanced again I think… -- 85 賽季 8 天
--
(翻譯)
(翻譯 EN)
+0
比賽1) Komanda dažnai naudojanti spaudimą pavargo žymiai mažiau nei komanda prieš kurią spaudimas buvo taikomas.
2) Absoliuti dauguma chronologijos įvykių rodo, kad taikant spaudimą atakos baigiasi tik SG arba PG metimu (iš padėčių, iš kurių jie net neturėtų mesti). Įtraukimas kitų žaidėjų į atakas prasidedančias aikštės spaudimu labai menkas (negi aikštės spaudimas taikomas visas 24 sekundes? Net ir tokiu atveju randami laisvi kitų pozicijų žaidėjai...). (Puolimas nebuvo statytas per gynėjus.) -- 85 賽季 13 天
--
(翻譯)
(翻譯 EN)
+0
比賽Taktika: greitos atakos - vidutiniškai;
Statistika: greitos atakos 0/0;
Pirmame ir antrame kėliniuose dar bandė po 1 greitą ataką kurti, bet neišsivystė. Tuo viskas ir baigėsi. -- 85 賽季 15 天
--
(翻譯)
(翻譯 EN)
+0
比賽In this game best players or important players, who should play at the end, came to the game on last minute when there was only 39 sec left to play. By the way there was couple more posibilities to change player when there was 3min (or less) left to play but it woulnt happened, I believe engine is working not very well on this situation -- 86 賽季 21 天
--
(翻譯)
(翻譯 EN)
+2
One more thing, why there is no more news about what was changed in the new engine?
--
86 賽季
21 天
--
(翻譯)
(翻譯 EN)
+4
比賽4Q 7:52 Estr Foul when fighting for rebound. In the future the player will have to be more cautious (5 f ): A. Palencia
4Q 7:52 L2T Foul against: S. Nve
4Q 7:52 Estr logotipas Substitution out: H. Herruz ( C)
4Q 7:52 Estr logotipas Substitution in: G. Torin ( C)
4Q 7:52 Estr logotipas Substitution out (fouls' limit exceeded): A. Palencia ( PF)
4Q 7:52 Estr logotipas Substitution in: P. Ausējs ( PF)
Herruz (C)
Torin (C-PF)
Ausejs (SF)
I think it's more normal do first the substitution of Palencia (5th foul) before Herruz for Torin and avoid the situation of Ausejs in PF to the final of the match. -- 86 賽季 29 天
--
(翻譯)
(翻譯 EN)
+0
vieninteli dalyka pasakysiu, daug senu zaideju gryztu, jei paleistumete sena versija. paleiskite sena varykliuka ir ten bus norinciu zaisti, o naujame, nera tiek norinciu. ne visada atnaujinimai yra gerai. padarykite 2 varikliu versijas, ir pamatysite kas zaidejams patinka. garantuoju, dauguma pasirinks sena versija.
--
86 賽季
29 天
--
(翻譯)
(翻譯 EN)
+1
Apie 23 sezono variklį, kur gynybos įgūdžiai neturėjo efekto.
--
86 賽季
29 天
--
(翻譯)
(翻譯 EN)
+6
Nelabai turi ir naujam. Kamuoliu peremimas isvis nuimtas sakyciau. Zaidejo su 13 diq dabartiniam varikly vidurkis 9. Naujam - 2,5...
--
86 賽季
29 天
--
(翻譯)
(翻譯 EN)
+4
Apie ta kur gali ir scautinti, gauti garantuota, db prikista visokio sudo, ne kiekvienas nori tiek laiko leisti zaidimui. Anksciau pirkdavau kreditus, db neperku. 4 sezonus kaba naujoko gidas, ale nesinuomuoju arenos ir niekas nesidomi
--
86 賽季
29 天
--
(翻譯)
(翻譯 EN)
+1
Turbūt tau reiktų pilnai įskaityti į naujoko gido sąlygą ir ją paeiliui atlikti. O jei tai bugas, būk malonus ir informuok apie tai administraciją, o ne lauk 4 sezonus.
--
86 賽季
29 天
--
(翻譯)
(翻譯 EN)
+3
Paspaudžiau 10 iš eilės komandų. Naujoko gidą perėjo 8 iš 10. Neperėjo 6 ir 4 wl komandos, o visi kurie nuo 1 iki 3 wl puikiai atlikę ir kažkaip apėjo šitą kaip tu sakai bugą (kurio iš vis nėra).
--
86 賽季
29 天
--
(翻譯)
(翻譯 EN)
+0
Klausyk, ar as toks kvailas? Kai neuzskaito nuomuotos arenos? Ar dar 5 issinuomuoti reikia?
--
86 賽季
29 天
--
(翻譯)
(翻譯 EN)
+0
Matomai kažką ne taip darai :D visiems pereina, o tau vienam ne
--
86 賽季
29 天
--
(翻譯)
(翻譯 EN)
+2
顯示隱藏回應: 159
Perėjau naujoko gida praeitą savaitę matyt kažką blogai darai
--
86 賽季
29 天
--
(翻譯)
(翻譯 EN)
+8
the new engine is completely missing of Blocks as well.
totally unrealistic. -- 86 賽季 30 天
totally unrealistic. -- 86 賽季 30 天
--
(翻譯)
(翻譯 EN)
+2
+0
未知的球員
+0
+0
球員:
交易後開始在新球隊比賽
--
84 賽季
21 天
--
(翻譯)
(翻譯 EN)
+0
球員:
交易後開始在新球隊比賽
--
84 賽季
21 天
--
(翻譯)
(翻譯 EN)
+0
I needed a Point Guard for the near future and traded my most expensive player at the time. I was bankrupt and had already lost my top 3 players, so I had to make a good trade as soon as possible. Whoever tried to report my this trade is probably just mad I didn’t give them Cely for nothing. This was the only decent trade I could find. A player that has forward size and point guard ball handling was a no brainer for me, so long as he was already lended out and wouldn’t cost me more than 2000 a week this season. I had to trade for a player that could contribute to my team immediately next season, but also has the ability to improve the next few seasons. Kalnietis also fits the game plan of my team because I have a team that will shoot a majority of 3s, so I needed high IQ guys that could shoot. Pairing Kalnietis with my recent draft pick and the improvement of my other high potential players will be more than worth losing one big man that I was going to lose for nothing anyway. Also, Cely is a Center in a Power Forward body. He doesn’t have the size or defensive potential to contribute long term on a team full of shooters. 6’9 finishers need a pick and roll offense and a dominant defensive big man to pair with. I’m a basketball player in real life, so I understand overall is not the only thing that matters in basketball. The individual skills each player has are the most important thing to look at when predicting a players’ impact. If I didn’t go bankrupt, I’d still have 3 players above 200 and therefore would have kept Cely. Sadly, I went bankrupt and lost almost all of my talent. I was lucky to pull this trade off and not lose Cely for nothing. Mind you, had I not done this trade, I’d have been left with only 2 players under contract for next season in Johnson and Makie. I was lucky to be able to reaquire Spettell in the free market and wouldn’t have been able to if I traded for a player that wasn’t lent out. I still have a negative balance and was positive for only the day I placed bids on Spettell and the big man. Had I not gotten either of them, I would have had to bring up my 16 and over prospects from my basketball school. That would kill their rate of growth. Lastly, the trade restrictions were very strenuous so I literally could only make specific trades regardless. Whoever reported this trade is a hater. I had a player harassing me while I was bankrupt, attempting to trade for all my good players before I lost them, yet he was offering terrible trades that would greatly hurt my team and financial situation. I will be providing his team name and username here as well.
--
84 賽季
35 天
--
(翻譯)
(翻譯 EN)
+1
Manager: trw542003
The Vietnam Veterans team manager was constantly harassing me and offering me terrible trade offers while I was in possession of my 3 high tier players. -- 84 賽季 35 天
The Vietnam Veterans team manager was constantly harassing me and offering me terrible trade offers while I was in possession of my 3 high tier players. -- 84 賽季 35 天
--
(翻譯)
(翻譯 EN)
+0
He tried to make stupid trade offers to me as well. If he has the nerve to report a trade, he shouldn’t even be allowed on the game. Every trade he offered me has been unfair. This is hilarious to me. You probably didn’t even need to give such a pristine explanation lol. I don’t know how the trade could be considered unfair anyway. Cely hasn’t even played anywhere near as good for me as for you anyway.
--
84 賽季
35 天
--
(翻譯)
(翻譯 EN)
+0
顯示隱藏回應: 7
How the Fair Play Committee members voted:<br />
- volunteers voted "Revert and punish": 0<br />
- volunteers voted "Revert": 2<br />
- volunteers voted "Fair": 6<br />
<br />
These reasons were chosen by the volunteers during voting:<br />
1 - Suspicion that trade’s goal is to help one of the teams<br />
1 - Overuse of disbalanced trades. Players' trade somehow has to benefit both teams (financially, in respect of team composition, etc). Good but expensive player can be traded to a bit worse but cheaper player. This type of trade can not be overused.<br />
<br />
-- 84 賽季 35 天
- volunteers voted "Revert and punish": 0<br />
- volunteers voted "Revert": 2<br />
- volunteers voted "Fair": 6<br />
<br />
These reasons were chosen by the volunteers during voting:<br />
1 - Suspicion that trade’s goal is to help one of the teams<br />
1 - Overuse of disbalanced trades. Players' trade somehow has to benefit both teams (financially, in respect of team composition, etc). Good but expensive player can be traded to a bit worse but cheaper player. This type of trade can not be overused.<br />
<br />
-- 84 賽季 35 天
--
(翻譯)
(翻譯 EN)
+0
對借入球員的球隊的評價: 
未知的球員