Feedback On Coding/Spriting/Player Projects in Discord
#1
Okay, this post is mostly around suggestions for Discord on spriting/coding/player projects. Posted in Admin Feedback, since it's really up to Admins/Devs to decide on these, but requesting feedback from anyone

Also, the whole topic is tricky in regards to time availability, I'm trying to not suggest direct time commitments here but I think some is inherently needed

~~

1. Better availability notice for coding/spriting in Discord
People looking to code something needing sprites may need someone to sprite for them or the other way around, but there's no good way to request this at the moment other than either 
1. Pinging specific people (which is a strong way to guarantee a yes/no response) or 
2. Putting a request in the coding/spriting channels (which often there will only be a response if someone who is checking discord daily sees it and is interested)

This leads to some projects being incompletable due to one of them missing

I think it would be more helpful to do one of the following:
1. Add an "Available for coding" or "Available for spriting" role to Discord for people to take, where pinging that role will let those available see if they're interested
2. Add a channel thread or Player Project posts dedicated for coding/spriting requests
3. Add a "Code help requested" or "Sprite help requested" GitHub label, so that people can easily add it to a PR they have in draft or in work

2. More dev involvement in player project approval/disapproval
Looking at player projects, while this is more of a smaller thing, I don't believe there is enough/proper use of the Dev Approved tag. There are some posts, like constructible atmospherics, as well as Flockmind, that haven't used this tag. You could say this is more of a pedantic issue, but if not being used properly, why does the tag exist?

Additionally, I think there should be a Dev Disapproved tag, or more solid involvement in dev disapproval, of projects. While maybe disappointing to receive a disapproval on your project, I think it would help those working on a project know that their project just isn't the best for the game, rather than spending weeks waiting for a response that may never come, or arbitrarily pinging devs that may only provide their response, without the whole dev team providing a unified approval/disapproval. 

There are many projects in the Discord right now where people have started them and then they just "staled". Though, this is the player projects channel in Discord where people can get more solid feedback on their projects and may spend significant time working on them, I feel this is the exact place where devs should be providing direct feedback, not just when pinged directly but in general. Additionally, I feel there's more of a problem in that devs may provide feedback, but is more of a individualized "not too interested" or "think this could be better in regards to xyz" response from devs, rather than a formal "Approved with xyz changes" or "Disapproved"

To help with this, I think there could be at least
1. A "Looking for Dev Approval" tag for players to add to projects, for devs to add a Dev Approved or Dev Disapproved tag to replace it with, when the player is ready. However, for this to work, there needs to be an active and formal "Approved" or "Disapproved" involvement in projects

~~

Also, to add to my personal experience in the above. I recently started a project "Space Phoenix Antagonist", which I've coded somewhat and made a PR for. I am not calling out the developer here, nor am I mad at them, but I started coding this because I pinged a developer for their input and they told me that it would at the least be good for a playtest (I was expecting an event like was how one was held for brainslugs). It took me 3 days to code. However, instead, I've been waiting close to 2 months now for a formal playtest. If you check the thread history for this project the past 2 months have just been me pinging devs asking for a playtest. I have no knowledge whatsoever of any testing that was done for this by devs/admins, which there has been at least some, and the feedback has not really been provided to me on improvements that need to be made. Nor has the developer who I originally pinged for input been involved with testing this.

While the essence of lack of interest (maybe? I don't really know) in this is not a problem, the problem is how it's gone.

I'd be lying if I said that I wanted to discontinue this project, because I really don't and I want to finish it. However, it feels like a terrible experience (as well as being this involved on something I'm not even a formal dev for) to work on something like this. As a contributor, how am I supposed to feel about working on projects of similar scope? I feel like I've done everything required and expected beforehand for a project of this nature (except maybe for not pinging multiple devs??) but yet the outcome has been not great so far


This post isn't meant to be emotional or anything, it's just my personal observance of what I've worked on and of how things go in Discord. Thanks for reading and consideration.
Reply
#2
(02-02-2025, 07:14 AM)FlameArrow57 Wrote: 1. Add an "Available for coding" or "Available for spriting" role to Discord for people to take, where pinging that role will let those available see if they're interested
2. Add a channel thread or Player Project posts dedicated for coding/spriting requests

In my personal opinion, this is what the #imxyz channels are for. Others might disagree though. This is worth further thought, for sure.

(02-02-2025, 07:14 AM)FlameArrow57 Wrote: Add a "Code help requested" or "Sprite help requested" GitHub label, so that people can easily add it to a PR they have in draft or in work

Are people really trolling GitHub to find projects to help with? I'm not aware, but if they are and this would help, we can look into adding this.

(02-02-2025, 07:14 AM)FlameArrow57 Wrote: 2. More dev involvement in player project approval/disapproval
I don't believe there is enough/proper use of the Dev Approved tag. There are some posts, like constructible atmospherics, as well as Flockmind, that haven't used this tag.

I envisioned this tag to be where a player can create a design document, have it approved, and then be confident that they can spend a dozen hours working on it without fear of it not being merged. I basically translate it to as "we like this, and will actively work to get it merged when done".
Flock didn't exist at the time this tag was created, and as far as the atmospherics - multiple PRs have taken a while to get to because we weren't sure about the design/code.
There have been multiple succeeding cases, such as nuke reactor, conveyors, and the current speech code rework.
In my opinion, if people want to be sure their work is not in vain, they should seek approval. If they're fine with it not being merged due to a design issue, then they don't need to.


(02-02-2025, 07:14 AM)FlameArrow57 Wrote: Additionally, I think there should be a Dev Disapproved tag, ... 

I think if you seek an approval and don't get one, this is the same as a disapproval. I don't see a need for a tag.

(02-02-2025, 07:14 AM)FlameArrow57 Wrote: There are many projects in the Discord right now where people have started them and then they just "staled".

To be a bit blunt, I think a lot of these projects have just staled due to effort no longer being put towards working on them. This is an inevitability with an at-will community-developed game, in my opinion.

(02-02-2025, 07:14 AM)FlameArrow57 Wrote: I feel this is the exact place where devs should be providing direct feedback, not just when pinged directly but in general.

I agree. Personally, a reason why I have not given feedback on multiple player projects is purely just because I'm not super interested/engaged by them.
As we're all volunteers too, I only have so much time in a day to work on SS13. I could either:
  • Review a project that doesn't sound interesting to me
  • Review an interesting project I want to help with/get merged
  • Work on personal projects

Personally, I think the latter 2 win every time.
I hate that my feedback here is that the projects should 'be more interesting', but I'm not sure what else to say - this applies to getting contributions from other players also.
One way or another, this has always been how PRs have been merged across SS13.

(02-02-2025, 07:14 AM)FlameArrow57 Wrote: devs may provide feedback, but is more of a individualized ... "think this could be better in regards to xyz" response from devs, rather than a formal "Approved with xyz changes" ...

This is because we're being careful not to speak on behalf of the 20 other devs - without a design document (Developer Approved) there's nothing we can bring to the group show and tell time and say 'we like this'.

(02-02-2025, 07:14 AM)FlameArrow57 Wrote: To help with this, I think there could be at least
1. A "Looking for Dev Approval" tag for players to add to projects, for devs to add a Dev Approved or Dev Disapproved tag to replace it with, ...

I think this is a good idea, with the caveat that I think a lack of approval is the same as a disapproval.
I think there could be better guidelines/processes on how to request an approval. Maybe a form, but I need to think on this more.

(02-02-2025, 07:14 AM)FlameArrow57 Wrote: I have no knowledge whatsoever of any testing that was done for this by devs/admins, which there has been at least some ...

We technically have a 'testmerged' github label that gets applied/removed when testmerging a PR. I wish there was better tracking, and perhaps that could come to the Goonhub round page in the future - with linking to the PR somehow.

--

I'm not too qualified to speak on the rest so I will let others respond.
Reply
#3
(02-02-2025, 12:10 PM)ZeWaka Wrote:
(02-02-2025, 07:14 AM)FlameArrow57 Wrote: Add a "Code help requested" or "Sprite help requested" GitHub label, so that people can easily add it to a PR they have in draft or in work

Are people really trolling GitHub to find projects to help with? I'm not aware, but if they are and this would help, we can look into adding this.

I'm not sure, and maybe a less ideal suggestion, but I think it wouldn't hurt (though maybe better suited if there were a lot more PRs). I think it would be more helpful for smaller PRs that aren't Player Project sized but still need additional help at the least. Unless something that requires 2 people should always be considered a Player Project. If Player Project usage of "Help Wanted" tag doesn't get additional help often then maybe it'd be an indicator for how this would go.

(02-02-2025, 12:10 PM)ZeWaka Wrote:
(02-02-2025, 07:14 AM)FlameArrow57 Wrote: Additionally, I think there should be a Dev Disapproved tag, ... 

I think if you seek an approval and don't get one, this is the same as a disapproval. I don't see a need for a tag.

I think I worded this in a wrong way. The suggestion was more at receiving an explicit "not interested" or "don't think this would work" feedback, rather than looking for or being ready for a response but not receiving anything. Not saying this hasn't ever happened.

(02-02-2025, 12:10 PM)ZeWaka Wrote:
(02-02-2025, 07:14 AM)FlameArrow57 Wrote: I feel this is the exact place where devs should be providing direct feedback, not just when pinged directly but in general.

I agree. Personally, a reason why I have not given feedback on multiple player projects is purely just because I'm not super interested/engaged by them.

This makes sense and I'm not saying there's a problem with it. I think that it's not always clear when working on a project if it's that there's a lack of dev interest, or if that devs haven't had time to look at the project

(02-02-2025, 12:10 PM)ZeWaka Wrote:
(02-02-2025, 07:14 AM)FlameArrow57 Wrote: I have no knowledge whatsoever of any testing that was done for this by devs/admins, which there has been at least some ...

We technically have a 'testmerged' github label that gets applied/removed when testmerging a PR. I wish there was better tracking, and perhaps that could come to the Goonhub round page in the future - with linking to the PR somehow.

Clarifying on this, I'm aware the code was testmerged and when. It just was not visible to me at how many times it was tested in game, no feedback from the tests given, and I was never notified of when any of it was happening. The other day I was given a comment on the PR itself of an experience in game from a dev, but I'm not sure from when it was, and it was a comment where I wanted to clarify the purpose of what was commented on
Reply
#4
(02-02-2025, 12:10 PM)ZeWaka Wrote:
(02-02-2025, 07:14 AM)FlameArrow57 Wrote: There are many projects in the Discord right now where people have started them and then they just "staled".

To be a bit blunt, I think a lot of these projects have just staled due to effort no longer being put towards working on them. This is an inevitability with an at-will community-developed game, in my opinion.

Yeah, people are gonna start and put down projects for a variety of reasons. If anything, streamlining a way to mark projects as "Abandoned" or something where there's open permission for someone to pick up what's already there and continue might help, but that's up to those individuals
Reply


Forum Jump:


Users browsing this thread: 4 Guest(s)