When you need a template
You do not need a template to build variations. Video Studio will take a body straight from the competitor library, or your own gameplay that you upload. Request a template when you want one of these two things:- AI variations of your own gameplay. A template is what makes gameplay recreatable, so this is how you generate more versions of it.
- A copyright free version of a competitor’s gameplay. The template turns their structure into an asset that is yours to use.
How a body card changes
The action on a body card tells you where that gameplay has got to:Requesting a template
1
Find the body
On the Body tab of Competitor research, filter to the gameplay structures you want to test. Sort by active days, since a body a competitor has run for months is a structure worth borrowing.
2
Select Request template
This opens the request modal, which gives you two ways to ask.
3
Choose Use as is, or Customise with references
Use as is asks for a faithful rebuild. The team matches the original closely, down to the detail: the same structure and pacing, the same motion, the same colours, and the same characters and objects on screen. Choose this when the competitor’s execution is what you want and you have nothing to change about it.Customise with references is for when you want to steer the build. It lets you attach up to 5 files as
jpg, png, mp4, mp3, pdf or html, which is where you show the team what your game looks like and how the level should read: gameplay capture, level art, UI screenshots, a style guide.It also gives you an Additional details field. A person reads this one, so write as much as you need: which mechanic to feature, which level to use, and how the gameplay should resolve.4
Send request
The request goes to the UAG team. Once delivered, the card’s action changes from Request template to View templates.
A template is built by the UAG team rather than generated instantly, so requests have a turnaround. Sending them early in a cycle keeps everything after them unblocked.
Plan around the request cycle
A rhythm that works well:- Request in batches. Send several template requests in one sitting. They progress in parallel, so you are never waiting on a single delivery.
- Request first, then carry on. Make template requests the opening move of a research session and work on hooks while they are in flight.
- Build a small library. Three or four delivered templates covering different gameplay structures will serve many test cycles, re-paired with fresh hooks each round.
- Reuse across cycles. A template is a permanent asset in your game and stays available long after a campaign ends.
