Recent Posts by Gabriel Cesario
4,177 posts(s) found
When renewing the contract of a player that is unhappy in terms of his priority there is now a cap on how much more money he is going to ask for. The old logic was always doubling the value on every renewal, which is not really what we intended originally.
The forced transfer feature is finally complete! I recommend you read the corresponding section of our game manual to familiarise yourself with it. The bottom line is there is no player status anymore and in order to buy a player that is not transfer listed you need to pay a lot of money to the team and be ahead in relation to the player priority. You can only attempt such transfer once every 6 turns, you can find out how many turns you have to wait in your profile page (easily accessible by clicking in your name, for example, from the team info page).
MediumTicker unlocked!
MediumTicker is locked, I will look into it in an hour or so.
That’s probably been left there as a mistake, it is not in our plans to allow them to play friendlies :-)
That’s strange, the columns are still clickable for me! Maybe contact me in-game so we can discuss further via email or something.
I have no issues with that…how much do you reckon it should cost?
Man, I’ve seen many others far worse than you :-)
Plus I was with you in Croatia for a couple seasons when you were starting to have consistent performances in CL, but we never really stood a chance against the big clubs. Anyway, I’m sure other managers would have plenty of tips to offers!
Don’t rush it! It needs to be properly done…plus I have done nothing during the long weekend (public holiday here in Aussie on Monday) :-)
I have pretty much done the logic that determines when the player and club will accept a forced transfer, now I need to put all the boring restrictions around it.
With the flock of managers moving from Paraguay to Belgium it was only a matter of time…well done! I’ve personally sent Dimitri a congratulatory message for the perfect season PSV had, outstanding achievement that brought him to the first place in the manager ranking.
Should I add Luxembourg to complete the Benelux gang? :-p
I like the idea Joseppi! This is now in our TO-DO list ;-)
During the season tick the RubySoccer Football Federation will elect the World Team of the Season, picking the 11 best players from all over the world. The best player among those 11 will also be given a special Player of the Season award. The election criteria is a mix of player match performance and the one used to give stars to players, mostly relying on consistent good match performances.
The World Team of the Season will be displayed in the Hall of Fame screen (accessible from the Dimension menu) in a new tab called Players.
I agree Fabio, it would have to be a situation where the money offered would make a lot of difference to the club, so having a lot of money would also work as a “defense” against this kind of offer. I’m also thinking that of changing scenario “a” above (where the player and the board are satisfied with the offer), instead of automatically transfer listing the player the offer becomes a pre-contract with the player and he’ll be transfer listed when the contract is almost ending (maybe 12 turns before), so that the manager losing the player has some time to plan for a replacement if needed (especially important for goalkeepers). During this pre-contract period the offer cannot be withdrawn, the player contract cannot be renewed, other teams cannot bid for the player and the owner can decide to transfer list him earlier (for the price of the pre-contract offer, of course).
It would then be very similar to the way it is today, where you can still make a player from a managed team critical but he is not immediately transfer listed, just won’t renew contract. We need to be very clear about the rules, maybe a message on the offer screen when you’re trying to buy a non-listed player.
Values entered into transfer price and wage fields are now properly formatted as you type. For example, if you type 12000000 you will actually see 12,000,000 on the screen. This should help avoid mistakes of entering one less or one extra 0.
I agree with you Fabio and my idea of how to change this is more aligned with option 1. I believe the status system is not adding much value at the moment and I’m considering replacing it completely with the player priority system just introduced. It is still one-dimensional but easily extensible in the future to allow players with multiple priorities if need be. In summary my draft proposal is:
1) Purge the player status system as it is
2) Limit the number of non-listed offers you can make in a given period
3) When you make an offer to a non-listed player, your offer is weighed individually against the player current situation in terms of wage and priority
4) The transfer amount of your offer is evaluated by the team’s board taking into account the club’s financial situation
There can be four outcomes:
a) Your offer satisfies the player (much better compared to his current wage and priority) and the board (the amount of transfer money will make the board happy): in this case the player the player goes to “critical” and is automatically transfer listed by the amount you offered, even for human managed teams. You cannot change your offer and other teams cannot make an offer.
b) Your offer satisfies the player, but not the board: CPU teams will renew the player’s contract, human managed teams will be alerted the player wants to renew or be transfer listed and will have x number of turns to action it, if they don’t the player won’t renew anymore and will either have to be sold or let go by the end of his contract
c) Your offer satisfies the board, but not the player: for CPU teams nothing will happen, for human managed teams the manager will be advised to transfer the player by the board, if he doesn’t action it in x turns his manager performance will be reduced by a given % amount, but nothing else will happen
d) Your offer does not satisfy the board nor the player: for CPU teams your offer will be rejected and for human managed teams it will just stay there for the manager’s knowledge, but will have no other effect
This is just a draft idea and needs deeper analysis and explanation. In addition to addressing the “friends bidding together” issue we want to make it possible for more managers to “steal” players by themselves, but without making it too easy. Happy to receive feedback, as always!
Thanks Fabio for your nice words! I agree with most of what you’ve said and I’d like to add that we understand there are still some challenges for newcomers and especially for those not quite there yet. I’ve seen some decent managers trying hard to be part of the elite in some leagues and not being able to do so. Of course, this is part of the challenge and fun, but our job is to make sure the opportunities are there for them to grow and get there and not just keep being frustrated. On the other hand, it’s a real treat when I see someone who had some tough seasons in smaller leagues against CPU teams and now is able to compete internationally at the same level as the big clubs!
Too long, didn’t read: thanks for your words, if you’re reading this and you’re new or frustrated for not being a top manager yet don’t worry, we are planning ways to improve the game experience for you ;-)
CPU teams will ask for higher values when transfer listing a player whose status became critical. This is the first of a series of initiatives that we know need to be done to make CPU teams a bit less dumb. We still want them to “help” managed teams a little bit, but their lack of planning is not good for the health of the game overall.
You can now postpone the retirement of your players using rubies by clicking the new icon beside the retirement icon in the player info screen. The cost increases the closer the player is to 40 years old: 1 ruby if he’s 36, 2 rubies if he’s 37, 3 rubies if he’s 38 and 4 rubies if he is 39. You cannot postpone the retirement when he is 40 years old.
When you postpone the retirement you are guaranteed the player will not retire at the end of the current season. During the next season tick, normal rules will apply in determining whether the player will announce his retirement again, if you’re lucky he may not do it. As usual the chances of announcing retirement are higher the closest the player is to 40 years old.
Newly generated goalkeepers will have 30% more training evolution steps on average than existing goalkeepers. We didn’t change the overall number of times a player can improve so that means that GKs will have less steps requiring them to play matches as a result. As things current stand it is difficult in many occasions to fully develop a GK without compromising some of your official matches, this change is hopefully assist in addressing that in a few seasons.
I’ve seen worse before (and I have a bug recorded to investigate) where a player played a national squad match without even being from that squad’s country :-(
Thanks for reporting anyway, I’ll add this on top of the existing bug so it’s clear the issue is not only about different nationalities.
You now have an option to choose whether or not a scout search should become inactive when no players are found on completion. The default behaviour is to make them inactive and therefore all existing searches have been marked as such. If you want them to continue running in this situation just uncheck the box that says “Inactivate if no player found?” when creating new ones or editing existing ones.
Thanks Alexander for the suggestion.
Ah, got it! I’ll add an option for that in the search itself, turned off by default.
Scout searches can now also be completed using rubies. Bear in mind that there is no guarantee a player will be found, it all still depends on your search criteria. Similar to coach reports, the lower the progress of your scout search the higher the price: 3 rubies if current progress is between 0% and 33%, 2 rubies between 34% and 66% and 1 ruby if higher than 66%.
They already do, they are only made inactive if no players are found (in which case you probably want to change the criteria).
You can now use rubies to immediately complete coach reports: 2 rubies if the report progress is less than 50%, 1 ruby otherwise. As said before we don’t want RubySoccer to become pay-to-win. While early completion of coach reports provide you quicker insight on your players we do not deem it to be fundamental and decisive enough so that those not paying for it are unable to compete against those that are paying.
He’s an explorer! He wants to get to know people from other countries, travel the world! I know, it may sound silly if you think about real life, but these restrictions are there to add something different to the transfer market. RubySoccer has many things that do not resemble real life. For example, we don’t have restrictions on number of foreigners in the squad, south american clubs would never have that many europeans playing in their squads.
I have “lost” a couple players due to the new rules as well. One of them wanted to play in a high ranked country and there was Paraguayan club bidding who was able to hire him with a lower salary. The other one wanted a lower ranked manager, so a smaller club with a new manager got him.
Anyway, it’s a recent change and we should give it a time to see whether or not it is a good one :-)
Thanks for the detailed suggestions, it sounds really interesting! I’ll definitely consider all that is being discussed here as one of the next big changes :-D
Agree about goalkeepers, maybe just for them I could extend the amount of improvement provided by training and reduce the amount provided by match experience.
Instead of my option 2 above (which I probably wouldn’t want to do anyway) we could have the following (thanks Samir):
2) You have an option to “send a player” to gain match experience (without using money) and, after x turns (depending on coaching requirements, coaching level and how much he still needs to play to improve), he improves. During this period the player would be unavailable to be used by your team and you could only send one player at a time to gain match experience. Obviously the number of turns that it takes to improve this way should be more than if you were actually using the player in your matches.
I’m still a bit unsure about a youth league and the complexity it adds to the game. I’ve been thinking of a few ideas to try and address this issue, what do you guys think about these:
1) Allow the team to pay a certain amount of money to simulate match experience for a player. This should work ONLY for simple “play matches” requirement, not for play abroad, play for division 1, etc. The exact amount will vary depending on player quality, minimum coaching level requirement for next step and this action should be limited to once (overall, not per player) every x turns (maybe 3?). For example, I could pay 100k to simulate match experience to one of my players that need to play official matches, then I will only be able to do it again (for any player) after x turns. Players need to play a few matches to improve, so I’d have to do this the same number of times for him to improve.
2) Extend number of times players improve by training so that match experience is not required until a bit later than what it is today.
3) Allow you to offer an amount of money in your loan clauses for each match the player is used by the team loaning him. For example, I could loan list a player offering 50k for each match he plays.
My preference is for option 1, it is the simplest to implement and tweak as needed. Actually option 2 is simpler to implement, but I think it will reduce too much the control we have over player improvement, it would mostly happen automatically. Option 3 is not bad either in my view, but it requires a bit more work to limit the amount that can be offered and also make CPU teams “aware” of the new rule so they can make use of it (loan players with this option when they need a bit of money).