.meteorwith the meteor files. You do not need to touch those.
node_modulesthe files for the node modules in your app. You do not need to touch those. This directory should be in the
publicwhere you store static assets (e.g., images).
clientwhere you set what the players can see in the experiment.
serverwhere you manage the flow and resources of the experiment.
/clientdirectory will be ran on the client. The entry point for your app on the client can be found in
/client/main.js. In there you will find more details about how to customize how a game Round should be rendered, what Consent message and which Intro Steps you want to present the players with, etc.
/client/main.htmlshouldn't generally be changed much, other than to update the app's HTML
<head>, which contains the app's title, and possibly 3rd party JS and CSS imports.
/server/main.jsfile. In that file, we set an important Empirica integration point, the
Empirica.gameInit, which allows to configure each game as they are initiated by Empirica.
/server/callback.jsfile, which contains all the possible callbacks used in the lifecycle of a game. These callbacks, such as
onRoundEnd, offer powerful ways to add logic to a game in a central point (the server), which is often preferable to adding all the logic on the client.
/server/bots.jsfile is where you can add bot definitions to your app.
/publicis here to host any static assets you might need in the game, such as images. For example, if you add an image at
/public/my-logo.jpeg, it will be available in the app at