Skip to content

Putt Party paywalled in Discord? Heresy! Time to recreate it.

License

Notifications You must be signed in to change notification settings

Stephen-Hamilton-C/club-party

Repository files navigation

NOTICE

Club Party has ceased development for the time being. I wanted to create this because my friends and I loved playing Putt Party, and we were considerably upset when the game got paywalled. However, Discord Activities have been brought back, and thus the point of creating this game is now moot. I won't archive this repo, just in cause Discord pulls a corporation moment and paywalls it again.

Club Party

Club Party is a recreation of the beloved Putt Party from Discord's activities. However, it was recently paywalled behind Discord Nitro. So, this project was created, and it remains open source and free forever.

Setup

  1. Ensure you have Git LFS installed
  2. Install Unity 2021.3 or later - https://unity3d.com/get-unity/download
  3. Clone this repo
  4. Club Party uses Photon Unity Networking v2 for multiplayer. You'll need to create an account at https://dashboard.photonengine.com.
  5. Once your account has been created, click on the grey Create A New App button.
  6. Name it whatever you wish, but make sure the Photon Type is set to PUN. Then click Create.
  7. Click on the App ID and copy it. We'll need it later.
  8. Open the repo with Unity
  9. A PUN Setup window should appear. If it doesn't, Go to Window -> Photon Unity Networking -> PUN Wizard -> Setup Project
  10. Paste your App ID into this window and click Setup Project.
  11. A PhotonServerSettings asset should have just been highlighted in the project assets tab. You'll notice there is a picture in the same directory. Those are the settings I use for Club Party, if you wish to copy them.

Automatic WebGL Deploy

You may notice the deploy.py Python script sitting in the Assets directory. This is a special tool to upload WebGL builds to a webserver. However, in its current state, it is quite unportable. This will be fixed soon. See #1.