Share something useful with the PlayWeld community.

A clear description and a working example help other game makers decide whether your extension is right for them.

1

Start with one useful idea

Choose an extension, plugin, skill, or agent role. Show what it helps someone do, what they need to provide, and what access it needs. The Greeting Starter is a small first example.

Continue
2

Make sure it works the way you expect

Use the right package format and check its dependencies and permissions. A package that passes upload checks still needs to be tried in PlayWeld.

Continue
3

Help people decide if it’s right for them

Create an account, verify your email, and explain what your tool does and how to install it. Include its license, source, supported versions, and the checks you ran.

Continue
4

Send it in for review

Upload your package and submit it for review. If something needs attention, update the listing or package and send it back when it’s ready.

Continue
5

Keep people in the loop

Give each changed package a new version. Explain what changed, update the setup steps, and respond to feedback from people who try it.

Continue

Try a small plugin first

The Greeting Starter shows the basic steps a PlayWeld plugin uses to start, answer a request, and shut down. Extract the example, open a terminal in its folder, then send the three requests below one at a time.

node index.cjs
{"jsonrpc":"2.0","id":1,"method":"plugin/initialize","params":{"protocolVersion":1}}
{"jsonrpc":"2.0","id":2,"method":"plugin/tool/call","params":{"toolId":"playweld.greeting/greet","input":{"name":"Builder"},"context":{"taskId":null,"agentRole":null,"accessMode":"restricted"}}}
{"jsonrpc":"2.0","id":3,"method":"plugin/shutdown","params":{}}

Check that the greeting is what you expect, then try an invalid name to see how the plugin responds. This test runs the example by itself; it does not show how it behaves inside the PlayWeld desktop app.

Before you share it

  • State supported PlayWeld and engine versions.
  • Explain filesystem, network, and model access.
  • Include source, license, and reproducible checks.
  • Describe installation, rollback, and any limitations.
  • Keep screenshots and examples free of private project data.

100%

Use left and right arrow keys to browse. Press Escape to close.