Guide
Say It So It Builds: Phrasing Voice Requests in LaVoice
The wording craft behind reliable LaVoice creations: sentence order, plain words, one idea per breath, and how to reword a request the game misunderstood.

CONTENTS On this page
Grammar the Game Can Hear
LaVoice does not build wishes; it builds sentences. The recognition listens for parts it knows, weapons, behaviours, ammunition, effects, and assembles them in the order you speak them. Phrasing is therefore a gameplay skill with the same status as aim: a well-built sentence lands the first time, under fire, while a poetic one gets rebuilt three times in the open.
This guide is about the wording itself. The LaVoice mobile arena homepage covers the game's builds and modes; here we work on the sentences that summon your side of them.
Object, Action, Effect
The reliable order is object, then action, then effect or ammunition. A pistol that shoots grenades. A turret that launches exploding pigeons. A shotgun with six barrels. Each phrase names a thing the dictionary owns, a behaviour it can attach, and a payload it can price, in the sequence the assembler expects.
Front-loading adjectives and backstories muddies the parse. The game is generous with combinations but strict about finding the object first, so give it the noun early and decorate after. Our voice commands guide demonstrates this order across the standard builds.
One Idea Per Breath
Compound requests work, but every clause adds a chance to be misheard. The phrasing discipline of strong players is one idea per breath: build the base object, confirm it in your hands, then speak the modification as its own request. Two clear sentences cost the same blocks as one tangled one and fail half as often.
This matters most mid-fight, when excitement speeds your speech and blurs the words. A short request spoken cleanly at the worst moment beats the masterpiece you planned in the lobby. When even a short request is one risk too many, the typing mode guide covers the silent route to the same builds.
Plain Words Beat Clever Words
The dictionary knows the vocabulary of the game: standard names for weapons, parts and effects. Slang, nicknames and brand names may be understood someday, as the developer grows the dictionary from the phrases the community reports, but today the plain word is the reliable one.
Test your synonyms in quiet matches, not ranked ones. If your favourite word for a part fails twice, retire it and use the standard term. Pride in phrasing is expensive; the arena charges by the rebuild.
Rewording a Failed Request
When a request fails, change one thing. Slow down first, because pace corrupts more parses than vocabulary does. Then swap the suspect word for its plainest synonym. Then, if it still fails, split the request into its object alone and add the behaviour in a second breath.
Changing everything at once teaches you nothing and usually fails again, because you cannot tell which change mattered. The game's voice diagnostics, improved in the current build, can also tell you when the problem is your microphone clipping rather than your words, which saves a lot of unnecessary rewording.
Building Your Phrasebook
Every strong player ends up with a personal phrasebook: ten to fifteen requests phrased exactly the way that player speaks them, proven across dozens of matches. Build yours deliberately in solo practice, a few phrases per session, and write down the failures as faithfully as the successes.
A phrasebook is loadout design at the sentence level. When the fight turns and your hands are busy surviving, the phrases you own outright are the only ones that exist. Everything else is improvisation, priced accordingly.
Field Notes
Speak in the order the assembler thinks: object, action, effect. One idea per breath, plain words over clever ones, and one change at a time when a request fails. Phrasing in LaVoice is not flavour around the gameplay. It is the input method, and like every input method in every shooter, it rewards the players who practise it on purpose.
Quick Answers
Why does LaVoice misunderstand my requests?
Usually word order, pace or an unknown word. Name the object first, speak a little slower, and use the plainest standard word for each part.
Should I speak long detailed requests?
Split them. One idea per breath, object then modification, costs the same blocks and parses far more reliably under pressure.
How do I fix a phrase that keeps failing?
Change one thing at a time: slow down, swap in a plainer synonym, then split the request. Also check the voice diagnostics for microphone clipping.