Suggestions on where to start?

Learn Content
1

Hi folks! Trying to get involved in contributing to this project but I’m not sure what to do. I’ve been combing through forum threads, the Github issues, and the Codecks but I’m finding a lot of things that have been resolved / are in progress / have open PRs already.

Is there anything that could currently use some attention from someone who’s still learning Unity? And/or what’s the best way to identify tasks for myself?

2

It is true that in this late stage, it’s hard to get started “fast” with the project, as many systems are well interconnected and not super easy to understand.

One first question: what kind of stuff do you want to do? Programming? 3D? Shaders? Effects? …

3

I’m most proficient at programming, and would be able to do the most in that area. I’m already up to speed on stuff like the state machine system and using colliders to trigger behaviors.

I’m interested in learning more about the graphics side, but would probably be better off tweaking or building on existing content than building something from scratch. (I took a 3D graphics course once, but that was a long time ago.)

Totally happy to help with brainstorming/prototyping gameplay systems, but as you said a lot of that is already in place.

4

Hi Guys, I like to participate in the programming aspect of the project. Do you have any suggestions on where to start coding?
I love to read codes and find out how systems are working. I try to catch up fast.

5

As said, it’s hard to identify where to “start” since many things are actually 80% done, and we don’t want to introduce new functionality.
I would suggest to try the game, play with it, understand how it’s built. You can refer to the wiki to get a basic understanding of many systems, the rest is in the code. The most useful thing right now would be to identify small bugs and fix them.

I’ll try to highlight small tasks. This is one for instance. (check the thread linked in the card too)
If you (and @randomscribe ) post here before working on something, I can provide feedback on the direction!

6

I just had a small idea that would be a nice to have, I created a task for it: Codecks
Let me know if it’s not clearly explained!

7

Thanks for the guidance!

I think I’ll take a look at the lightmap scale setter. I’ll probably be back here soon with some questions. :slight_smile:

8

First questions:

  1. Where in the project should this new component live?
  2. Are there any existing custom tools in the project that I could use as a reference?
9

Scratch question #2, I seem to have a handle on it now :slight_smile:

10

Here’s my PR: Add lightmap scale setter tool by pointfivetee · Pull Request #452 · UnityTechnologies/open-project-1 · GitHub

Obviously the script will need to be moved to its proper place before the PR is ready to go.

11

Great, you’ve been very fast :smile:
I like the simplicity of it, thanks. Makes it easier for us to review and approve, we can always improve it later!
Maybe you can place it in Scripts/EditorTools, there’s a similar component script that only has a use in the editor.

12

I’ve also come up with another small task. It’s very easy, so maybe you can leave it to somebody else who’s also wanting to get a foot in the project, so to speak.
https://open.codecks.io/unity-open-project-1/decks/15-code/card/1gk-camera-shake-on-hit

If you want a bit of a challenge though, there’s this new fresh bug that will require some thinking on how to fix it in a solid way: Codecks

13

Cool, it lives there now. PR branch has been updated.

14

I believe I have found a very simple fix – just have the AudioCue emit a “stop” event when its parent component is destroyed.
PR: https://github.com/UnityTechnologies/open-project-1/pull/455

15

Great entry tasks, I see both of them are done, It would be great if we have more tasks like these. :slight_smile:
Also, it’s totally understandable if there are no tasks available. I can also help in testing and finding bugs.

1 Like
16

Yeah, sorry for that, it’s not easy to come up with bite-sized tasks, and it takes time to write them up too :stuck_out_tongue:
But bugs, there’s plenty of them! Just think priority though, there are some bugs that it’s ok to leave out - for now.

There was this task actually that was never finalised: Codecks
Could be interesting?

17

Thank you, I’m not super good with shaders and colors but I’ll try to come up with a solution.
In case I failed I’ll go for the bugs

1 Like
18

I have created a PR for this: PR: https://github.com/UnityTechnologies/open-project-1/pull/476
Also, I have posted about it on this forum: https://discussions.unity.com/t/825049

1 Like