Anyone have SDS' ear?

[capa]

One item that I think is way overdue is the ability to port rosters from one yearly release to another. I don't mean Franchises...I mean just roster sets that can be downloaded and shared online.

This seems to have fallen somewhat on deaf ears and I was wondering if anyone can make inroads here with SDS. In the past they have said that it is too complex to take on, but I am not sure I believe that.

This can and should be done to save the incredible roster makers out here untold hours of reproducing the same sets each release.

I know new releases bring new player attributes, etc. These can be handled by setting default values for players in the new release version and allowing users to edit after the fact.

It may not be high on their priority list but maybe they could throw us a bone??

Anyone have more than just a casual tweeting relationship with SDS that can push this a bit?

C

[Caulfield]

Re: Anyone have SDS' ear?

One item that I think is way overdue is the ability to port rosters from one yearly release to another.

This seems to have fallen somewhat on deaf ears and I was wondering if anyone can make inroads here with SDS. In the past they have said that it is too complex to take on, but I am not sure I believe that.

This can and should be done to save the incredible roster makers out here untold hours of reproducing the same sets each release.

It may not be high on their priority list but maybe they could throw us a bone??

that was the old reason.
the new one is the dev team is too small.

[capa]

Re: Anyone have SDS' ear?

that was the old reason.
the new one is the dev team is too small.

Yes I did hear that too. A DB programmer could map this stuff out and get it working within a week. Ok...two weeks with testing.



C

[countryboy]

Re: Anyone have SDS' ear?

One item that I think is way overdue is the ability to port rosters from one yearly release to another. I don't mean Franchises...I mean just roster sets that can be downloaded and shared online.

This seems to have fallen somewhat on deaf ears and I was wondering if anyone can make inroads here with SDS. In the past they have said that it is too complex to take on, but I am not sure I believe that.

This can and should be done to save the incredible roster makers out here untold hours of reproducing the same sets each release.

I know new releases bring new player attributes, etc. These can be handled by setting default values for players in the new release version and allowing users to edit after the fact.

It may not be high on their priority list but maybe they could throw us a bone??

Anyone have more than just a casual tweeting relationship with SDS that can push this a bit?

C

I don't understand the bolded part. They have addressed why they haven't taken it on, but yet you don't believe them. So why bend their ear and inquire about it again?

It comes across that unless they tell you what you want to hear that you'll just not believe them as if they are lying for some reason or another.

[Juzbee]

Re: Anyone have SDS' ear?

Yes I did hear that too. A DB programmer could map this stuff out and get it working within a week. Ok...two weeks with testing.



C

So, in other words, one week.

[capa]

Re: Anyone have SDS' ear?

I don't understand the bolded part. They have addressed why they haven't taken it on, but yet you don't believe them. So why bend their ear and inquire about it again?

It comes across that unless they tell you what you want to hear that you'll just not believe them as if they are lying for some reason or another.

Because I do believe they are not telling the truth. This type of change is not too complex. It is db programming and mapping fields. I guess I was hoping they would reconsider if there was enough outcry and find a way to get things that are not relatively "easy" to them into the game if it is what folks want. Whether there is enough outcry for this is another matter. I can't imagine the roster makers would be against it, that's for sure.

I mean, many things the community has asked for must have been considered "complex" for them...yet many things were eventually through the years included. Being the squeaky wheel here could also get something like this done.

[countryboy]

Re: Anyone have SDS' ear?

Because I do believe they are not telling the truth. This type of change is not too complex.

There's no use in continuing this conversation after these two comments.

[capa]

Re: Anyone have SDS' ear?

There's no use in continuing this conversation after these two comments.

Thank you for your opinion. When a major publisher says updating db records is too complex, I do tend to disagree and think they are fabricating. My opinion. Sorry if you do not agree. You can move on from the conversation. Or PM me and we can hash it out there.

It's my opinion as well for sure...based on first hand knowledge and experience in the field.

Mods - you can close the thread. It's going to go in a bad direction.

C

[Culture Rot]

Re: Anyone have SDS' ear?

It really is as simple as you laid out. And MLBTS devs can be reached directly on Twitter. I don't believe the issue is them not knowing people want this though.