Have something to say?
Integrate Plushie Trading into Events
So I am not exactly sure what the best way to do this would be but my partner and I regularly will plushie giveaway’s at our events (where each person will get one plush of their choosing). Our biggest struggle is keeping track of who wants what plushie at the end of an event. Especially when people go straight to the UG after the event ends and doesn’t tell us which one they want until they get to the trading table Could there be a way that people can mark which one they want through PPA? I am not sure what the best way would be to implementing this but considering that you already have the trading system built in, maybe it wouldn’t be too difficult to add?
Host & Participant Review Statuses
Some party issues stem from communication gaps and mismatched expectations. Implementing a mutual review and status system allows hosts and participants to set clear expectations, evaluate past party interactions, and avoid disruptive players. Review & Status System Host & Participant Reviews: Enables hosts and participants to leave status updates and reviews for each other after a party. Informed Decision-Making: Helps players and hosts review statuses upfront to decide who to play with and set clear expectations before committing to a party. Disruptive Behavior Prevention: Allows users to flag or mark bad interactions, helping hosts and participants screen out disruptive players and avoid repeated bad experiences.
Upgrade Palia Party backend tech
At the moment all categories, activities, etc on Palia Party are manually added by me. Palia is a constantly updating with new features, items, recipes. And sometimes existing items and recipes change. It’s hard to manage so for the last month, I’ve been working on automating this process. The final piece of the puzzle is to map the existing Palia Party database to this newly automated structure. While changing structure, I’m also changing to a relational backend system schema. The schema restructure would help unblock so many features, like more granular party filters, blocking/following users, etc.
Ordering the list of finished parties
The order in which parties are displayed is hard to follow. This is a list of finished parties associated with a community. I see no basis for the order in which they appear, and one of the most recent is way down near the end of the list. (The Plot Pop-in Party) It might be useful if this was sorted by date?
Warn about overlapping parties
When a user signs up for a party that overlaps with another party that they’ve signed up to, show a warning.
Block user
Hide blocked user parties from being displayed Hide blocked user messages from being displayed in chat
Discord Notifications
Similar to https://paliaparty.featurebase.app/p/notifications but allow Discord notifications to be received.
Email Notifications
Similar to https://paliaparty.featurebase.app/p/notifications but allow emails to be received.
Distinguish between parties that allow drop-in and those that don't
A continuation of https://paliaparty.featurebase.app/p/flexible-party-durations This will allow parties to support "drop-in, drop-out" play by keeping parties active and signal to players that they may enter after the party has started. If players need to leave early, the party will remain visible, allowing new players to jump in and fill empty slots mid-party.
Chat position setting
On the desktop version of the website, previously the chat was located off to the far left. But with the introduction of ads, it was moved to be contained within the site main content area. Now with premium memberships, some users now have an empty, unused space to the sides. And some users don’t care for the overlapping of chat and ads, while some still do. It would make sense for the user to decide themselves where they want the chat to be positioned with a simple option.
Ban/block users from a party while not actively in the party
Allow party hosts to add difficult users to the banned user list, even when the user isn’t in the party. Currently it’s possible for users to create havoc and then quickly leave without any punishment to carry out against problem maker. This task aims to solve that issue.
Text formatting in party descriptions (Markdown?)
Currently, party hosts have no way to emphasize text (bold, italic) or create section headers or bulleted lists. Given the detailed information sometimes included in party descriptions (rules, expectations, what-to-bring, etc.), these functions would allow hosts to create descriptions which are easier to read, digest, and refer back to. The need is there: I’ve observed party hosts using special Unicode characters as a substitute for bold/italics and headers, which can unfortunately result in undisplayable or scrambled text on older devices (particularly older phones). If a WYSIWYG editor (i.e., where you highlight text and then click a button to format it) is too much, perhaps a limited version of Markdown support could be a good alternative, since folks have had a chance to familiarize themselves with it already because of Discord?
Automatically lock all roles at a certain time
To avoid no surprise sign ups, allow to set when the party automatically locks all roles. As default, all roles will lock when the party starts, but can be changed to any arbitrary relative time to when the party starts (e.g. “15 minutes before”, “24 hours before”, “5 minutes after”). This can also be toggled off, if the party allows drop in sign ups, but is toggled on by default.
Toggle lock/unlock all roles button
A quick way to lock or unlock all roles in a party for convenience
Export to Calendar
I would love to be able to export either a party page and/or my Signed Up Parties page to my calendar. Ideally, this would include: Event title: Party Title, some kind of divider character, Host Name Description: Party description, activity list, location, role(s) I signed up for Location: PPA link OR external Discord link specified by host (and, obviously, date/time) As an added bonus, this would be useful not only for players’ personal calendars, but also for quickly adding events to shared calendars integrated with Sesh, Chronicle Bot, etc. to manage native Discord events and reminders.
Copyable Discord UNIX timestamp codes for party date/time
When sharing a PPA link on Discord, it is currently necessary to go through many extra steps to generate a “fancy timestamp” code that will display the party date/time in the user’s timezone the way that PPA timestamps do. I propose adding a “copy timestamp” element to the party page (or an option to add one to the “copy party link” function) to streamline the process. (There are browser extensions that can make this easier, and the @time command on Discord, but neither of these options is available to mobile users.)
"Maybe"/"Interested" role
Currently, the only way to keep track of a party you have not committed to attending is to either bookmark the page (and remember to come back to it) or leave it open in a tab. If I don’t know whether I can come a party yet, sometimes this means that I lose track of it (especially when switching devices). An option to flag myself as interested in attending, but not able to commit yet, could put the party on my Signed Up list and mean I could easily find it again. This could also apply for External parties, allowing users to keep tabs on them until they have time/device access to follow the signup steps. If recurring parties are implemented in the future, this would also allow players who can attend for only some of the scheduled times to keep track of the party through the recurrences when they cannot attend. Currently, hosts could probably finagle this with the existing featureset by adding a second activity with a custom signup option (which would also be cool, if widely adopted), but having a dedicated option a host can enable for their party might be useful.
Build party: A new kind of party
We ran a build party recently (April 10/11, depending on timezone). It was a great success, but a lot of work. The idea of this party was that a plot was open for a long time. In this case, 14 hours straight! Participants in the party were able to come and go over that span, and they all had edit permission in the plot. Everyone worked together on a single theme. In our first instance of this kind of party, we made an airport. Participants are keen to continue with the project, so we will be running the party again, on the same plot, to keep working on it together. We had 12 people involved in building at the plot. For this event, the host needs to supply all materials, and had a plot that gets used. This plot should be set aside for the work to remain in place after the event. Editors can only move things around that are already on the plot. We managed this by setting up enormous stockpiles of items of all kinds people could choose from; and also by having the host make particular items on request. The host must also remain on the plot to keep it open; so before hand the host had to ensure a very well stocked supply of materials (planks, bars, bricks, fabric, and all kinds of forage items that might be used to make decor). This party is a major commitment for anyone wishing to host, but the end result was a really fun day with lots of co-operative work going on and some really creative building, at all levels (advanced, and beginner). Next one will be easier, as I already have a large stock of decor in storage from setting up the first time. Not everything gets used; anything that is used remains on the plot in any case.
Dish Sell Value calculations (and other dish-related values)
This is a long shot, but writing up the ingredient variables made me think of it: If you know what specific ingredients are going into a dish, it is 100% possible to predict the unstarred and starred dish sell values. (It’s not 100% possible to predict the star rate… yet. I’m working on it.) Given that PPA already allows hosts to specify different ingredients to be used, it could also potentially calculate the dish sell values. This could be useful to hosts (i.e., help choosing what fish, mushroom, etc. to use, either to ensure consistent stacks, or to avoid the Ancient Koi “rare fish that doesn’t make you money” trap) and useful to prospective partygoers (“Will this food stack with the stuff I already have?” “How much more is this hour-long poke party worth than than this 40-minute sashimi party?” “Is this for selling or for eating?”) I have a whole writeup on this based on Dalia del Rosa’s initial findings and my own further research after the Luna New Year 2024 and Elderwood updates, on this Google Sheet. The main wrinkle is that there are a few very weird exceptions to the rules — Stuffed Cabbage Rolls and Spicy Honey-Baked Muujin come to mind, as well as several vegetables that don’t contribute properly to the dish sell value when chopped. So it’s not as simple as just plugging the unstarred sell values of all the ingredients into the formula. Building on this concept, it would also be nice if hosts could choose to display any combination of the following on a cooking party: Focus amount granted if you eat the dish (starred and unstarred) — I seem to remember that PPA used to display this, a long time ago? Dish sell value (starred and unstarred) Estimated expected star rate (a percentage — can’t calculate this yet, but experienced partygoers will have a pretty good feel for it and could enter it manually) Expected revenue (by combining the previous two bullet points and the dish quantity) OR minimum/maximum revenue (based on 50% base star rate for the minimum, and 100% star rate for the maximum) Expected duration (iirc you already have this planned!) Base XP per round/per item (fixed values — always the same every time the recipe is completed), which also tells you how much focus each cooking round consumes Expected XP for the whole party before focus bonus (previous item x dish quantity) (The last two could also apply to charged flow tree parties, where instead of dish quantity, it’s # of trees.) While we’re dreaming, perhaps at some point these items could be used to filter parties: I need to make 150k gold in the next 24 hours to complete this building project — show me all the parties over 50k revenue with duration under 60 minutes from this date to this date In all truth, I probably should be looking into writing my own tool for this — but since it could also be a potential value-added for PPA, I figured I’d float it by you anyway. :)