Warrior General Games

Today, when you copy an OAI (for a different team or new gameplan) but want to maintain your current OAI/Packages, you have to copy all of the Packages then replace them in the OAI one-by-one.

Suggestion: Add a Copy AI/Packages button that allows you to duplicate an AI and all Packages within it.

This would save coordinators a ton of boring, repetitive time.

yes

+1

+1

+1 billion dollars

omg gold +1

+1

Happy to see the support.

Was half-expecting someone to say this was already possible, then I was going to feel like a HUGE donkey.

No idea why this hasn't been implemented yet - such a tedious process and seems like an easy fix.

+1 I would like to see it done on defense as well. It would be great even if they were empty packages.

Originally posted by _OSIRIS_
+1 I would like to see it done on defense as well. It would be great even if they were empty packages.

Defense would be harder since plays would have to be copied in addition. That would require an existence check for the play since it could be in multiple packages. It could be done (as is) but it would be complicated. An easier solution to code (but probably harder to implement) would be to redesign the database schema so that each play (or package or AI for that matter) is saved only once and tied to the user only. If a coordinator grants AI access to the team, plays, packages, and AIs are made available to that team.

OK, I'm going to stop now or I'll end up putting together an entire technical database design here...

Originally posted by AirMcMVP
Defense would be harder since plays would have to be copied in addition. That would require an existence check for the play since it could be in multiple packages. It could be done (as is) but it would be complicated. An easier solution to code (but probably harder to implement) would be to redesign the database schema so that each play (or package or AI for that matter) is saved only once and tied to the user only. If a coordinator grants AI access to the team, plays, packages, and AIs are made available to that team.

OK, I'm going to stop now or I'll end up putting together an entire technical database design here...

Agreed - the coding logic would have to blow down through all levels of Ai, packages and plays and would need to be linked to the user. This is a good suggestion, yet difficult to implement

Originally posted by AlBarsch
Agreed - the coding logic would have to blow down through all levels of Ai, packages and plays and would need to be linked to the user. This is a good suggestion, yet difficult to implement

Eh. Implementation would be easy.

User AI Table with a primary key of userAI_ID
User Play Table with a primary key of play_ID
Package Table with primary key of Package_ID
Team table (presumably exists) with primary key of team_ID
Mapping table that took the userAI_ID and the team_ID along with a terminateDate (set to Day 40 of current season if owner/co-owner removes the coordinator as a GM and to "today" if the GM removes himself.

Honestly, this is probably similar to how user AIs are currently shared with teams. They should just remove the concept of team AI and this problem would solve itself.

Originally posted by _OSIRIS_
+1 I would like to see it done on defense as well. It would be great even if they were empty packages.

That is why I mentioned empty packages. Everything would load except the plays which you would have to add manually.

yes please