Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Sorry, follow up question, does this contradict when I have two or more puppets on one card?

because when I do a:

pt.command[deck
"!show NAME1 EMOTE customPOS1"
"!show NAME2 EMOTE customPOS2"
]

only the first line (whichever comes first) gets executed.

On this occasion though:

pt.command[deck
"!show NAME1 EMOTE customPOS1"
]
pt.command[deck
"!show NAME2 EMOTE customPOS2"
]

both can appear just fine.

Might be some other problem in my design, still checking it out, but shooting the question first)

ah and also trying to show any puppet with stage directions results in them snapping to "topleft" instead of the assigned place. Custom positions work fine.

Moving any puppet from offstage to custom position is also odd? I tried with boxy in the guided tour, but rather than "move from offstage to custom position" it did a diagonal line downwards. Not sure what I'm doing wrong here, but I have so much questions.

If you want to issue multiple commands with one call to pt.command[], the second argument will need to be a list of strings. Placing a comma between strings joins them together into a list, even if they're spread across multiple lines:

pt.command[deck
 "!show NAME1 EMOTE customPOS1",
 "!show NAME2 EMOTE customPOS2"
]

The above is equivalent to:

pt.command[deck ("!show NAME1 EMOTE customPOS1","!show NAME2 EMOTE customPOS2")]

ah sorry sorry, that was me being unobservant, thank you for the reply!

Sorry the stage position question persists. No matter the POS I give to any puppet they snap to the "topleft" of the screen. CustomPOS works fine.

Carefully check the spelling and capitalization of the positions you're specifying against the diagram of stage directions, and that the arguments to Puppeteer's commands are in the correct order. For example, !move takes a POS as its second argument and does not alter EMOTE, while !anim does not take a POS argument or an EMOTE argument.

There are a number of working examples in the documentation; you could try changing them bit by bit to approach your use-case. If you're getting yourself confused by a complicated project, try making a new deck from scratch and assembling the smallest possible example that demonstrates the problem you observe.

Thank you for your infinite patience!

I actually found out that the "snapping to topleft" problem seems to be a browser/desktop issue for a prior version of decker. I've updated to 1.41 and it is fixed for me!

Again much thanks to all the helpful answers and being so encouraging! Hope you have a great day🏃

(for reference, how the desktop version behaves before I updated:)

Glad you were able to resolve your problem!

Be aware that importing modules into your decks adds a copy of the module to your deck; occasionally Decker release notes may point out updates to Dialogizer, Puppeteer, or other modules that are included with Decker. If you want to be certain you're using the latest version of a module, you can use the Resources dialog to remove dd/pt/etc and then re-import them.

(+1)

yeah I did that thank you!