Global Moderators group

Paul Winterhalder

@moondory77 - why would you need/want to update a tournament in progress?

We consider the tournament to be a contract between the player and the game dev. You enter this tournament. You have <X> hours to compete. And you can win <Y> in prizes.

Changing the rules half-way through the tournament seems unfair? You are changing the duration? The prizes? These are both things that the player did not agree to.

Anyway - that was the assumption of the system - and it's why once a tournament is started any changes you make to the tournament get queued up for the NEXT tournament cycle, not the current one.

That said - divisions are even more complicated - as even if we wanted to there would be potentially thousands of records to update to make the change.

I need to better understand your use case to consider this request.

Paul.

Paul Winterhalder

@noah - the servers have been patched. You now have the option to exclude division set configs during deploy.

Paul Winterhalder

Hi @noah - just checked and it's still in test. I'm checking with the team.

Paul Winterhalder

Agreed @armitage - the bulk messaging feature is planned for the use case you describe... (and yup - still coming ).

Paul Winterhalder

Hi - you custom entity based solution for this is sound.

You also might want to check on the messaging system - which has an "inbox" and a concept of whether entries have been "read" or not. It might do what you are looking for more directly?

Paul Winterhalder

Note - the client devs have asked me to point out that this serialization challenge is only for folks using LitJson. All the other libs seem to handle things just fine.

Paul Winterhalder

Hi @LEE-JONG-GUN - did you have any luck with that?

Paul Winterhalder

Hi Lee,

We are having difficulties recreating the issue.

Can you post an example JSON response where you are seeing the issue... it may help us to track down what it causing it...

Thanks,

Paul.

Paul Winterhalder

Hmm - deployment is a very complex process - and in this case the complexity of picking and choosing what collection definitions get migrated over outweighs the complexity you would have to add a new field "week" to your collections and queries.

So apologies - but you should make the appropriate changes so that you have a "week" field in your collections (with appropriate indexes).

In compensation - I can offer up that:

We ARE adding the ability to exclude Division Set Configs from deploys (as you requested) <-- this should be available next week sometime.
And we DO now support migrating META data WITHOUT SCRIPTS via the builder API... (that got patched YESTERDAY!)

I hope you can understand.

Paul Winterhalder

What sort of edits are you doing to the leaderboards that updating multiple of them at the same time would be appropriate / convenient?

Global Moderators

Posts

Member List