Suggested

Add Transfers Filters!

This game is fueled by the numbers, but the transfer screen works only by wage, time, and star value.

--

On the drivers screen we should be able to filter by:

1. min talent!
2. min experience
3. if "buy now" is available
4. min / max age
5. min / max wage
6. min / max fee
7. min / max weight
8. min / max height
9. min / max rating (though, sorting is actually better for this case, so not really needed)

It would be nice to see a "last race" column added as well. Display date and result here.

--

On the staff page please add filter for:

1. Staff type! Or even better, have a different page for each type to begin with. On many other screens you nest tabs multiple levels deep, but for some reason you display this key information in the table. On top of that it is the only place you use an abbreviation, making it more difficult for new managers to find their replacement Chief Designer.
2. For chief designers add weakness and strength filters. Allow selection of multiple categories.
3. if "buy now" is available
4. min talent
5. min experience
6. min / max wage
7. min / max fee
8. min / max age
9. min / max rating (though, sorting is actually better for this case, so not really needed)

And for goodness sake, display the retirement age somewhere! It is scary bidding on a staff member when you have zero clue how long you can use them for!

(Lists ordered by importance with "1" being most important)

This is an interesting idea, but what does it accomplish? What would it mean? If a driver or staff has the stats you want what does it matter when they last were in race? They could have been in reserve for a season or they could be stuck in the transfer market. There are at least 500,000 downloads of this game now on Android alone; there are at least that many drivers out there on the market. while might be nice to know, it requires added coding but doesn't bring any value


Scary? Not at all in this game. Do you know when your favorite current driver is going to retire? Did anyone see Nico retiring? Look, you sign drivers and staff to 20 race contracts, which they honor. If they decide to retire at the end of a contract you have more than a season to find a replacement. If they decide to retire after renewing you have 50 races to find their replacement, that is almost 3 full seasons. That is quite a bit of advance notice.

As for the filters, it would be nice to have some filtering, but again, you aren't going to get a list of 5 drivers that match your criteria. It's going to still be around 100 to sort through. I can also imagine that a bunch of queries for drivers and staff would put a load on the servers. It may be that the transfer market would need it's own server to handle all that traffic

Um ok then. A SELECT query is very cheap database operation. Meanwhile training, race results, car upgrade requires an UPDATE query which is often twice as heavy.

I'm not sure what you are basing this statement on, but as someone who has wrote even more complex tools & databases, I can say for certain that you are wrong. This will not increase the server load enough to justify another machine.

No, and that isn't very constructive. This is a suggestion forum. I am talking about the current version of the game. If the developers don't want this kind of constructive (and exact) feedback, then they shouldn't have made such a forum.

Well then my suggestion is to offer to build the query system for the game.

The devs set up this forum for suggestions but when the same suggestions come up and the same explanation is given and no one does any research it gets a bit frustrating.

And the comment about the "old" version: in the web only version from before this was released as a mobile app had a few basic filters and the ability to sort by 1 attribute at a time.

Sure, but I did search the forums. I didn't see any suggestions as specific as this one.

If that explanation has come from the development team, then maybe link to where a developer said it to give your statement more credibility.

I'll gladly build such a query system. You do need to make a suggestions before implementing to allow for discussion, yes?