oh shi i forgot about that 
1 Like
Lol, what has this thread turned into…
1 Like
I love how threads that already have been solved get more views and replies than some that actually present problems the OP needs help with sometimes lol… You should mark it as solved so it gets locked, a lot of the replies here give lot’s of good advice on scripting already.
2 Likes
Yea, but it’s not really solved, nobody said a huge long thing with a solution.
2 Likes
The guy’s post got moderated. It disappeared from the thread. Oh well. His problem.
2 Likes
You should take a look at this post I made on a similar topic:
edit: Added quote of the linked post so it's available to readers who're not logged in ;)
2 Likes
hey so i know this is really off topic, but does anyone know how to put the script symbol next to your profile pic saying your a programmer?
2 Likes
Join the programmer group > Go to your profile > Preferences > Account > Title/Flair
2 Likes
I mean, the solution here is really subjective. Maybe you’re really good at one part of scripting but unaware on how to do another part. For example, I’m very aware of a lot of things regarding scripting but I still get stuck on others (I don’t even know how to make very complex math in scripting due to me still being in school and I still haven’t learned those parts yet)
1 Like
Id say start small. All your mechanics should be simple at first. Then as you get farther, you can go back and improve them as you learn more or get better ideas.
2 Likes
Well, the issue is that this isn’t something that can really be solved overnight. As @KLL3o stated, there’s lots of great advise on how to go about it. This is something that is going to take time.
One more piece of wisdom that I can give (I’ve been where you are, trust me). When it gets to a point where you’re feeling overwhelmed, just walk away for awhile to clear your head and come back to it later. That’s what I do.
In the Agile programming methodology, there is something called a backlog. In it’s basic form, it’s a to-do list. Just write down everything that needs to be done as a to-do list. As you complete each task, mark it off. If you find other things need to be done, add them to the list. That way you have a clear and concise list of tasks that are required to complete your project.
My list looks something like this:
Comp When Area Task
The fields are generally self explanatory, but I’ll list them out anyways.
- Comp: Checkbox to indicate that the task is completed.
- When: When the task was completed.
- Area: The area or module of the task to be completed.
- Task: A description of the task itself.
It really is that simple.
Hope this helps.
EDIT:
One other thing I forgot to mention. Make sure to document your code (add comments). Explain complex logic. Describe what each function does, what it’s parameters are, what it returns (if anything), maybe the conditions of specific returns like “Returns nil if not found or if there was an error.” kind of thing. That way, when you go back to it, it will be easier to follow what you did and why you did it.
4 Likes
would you recommend to write down the list digitally or physically? for you personally?
1 Like
I’m going to give my opinion about this matter here, I usually am too lazy too write docs dedicated to to do lists (don’t be like me, do it how Maelstorm described), so my own to do list are direct messages I exchange with my alt account on the blue gaming chat app which go something like this:
“Do the Parkour system”
“Add sounds to X tool”
“Finish enemy design”
2 Likes
If you’re working in a team, then digitally. You can use Google Docs for this. But also in a team, there’s two other fields that should be added: Assigned and Started. Because multiple people are working on it, you don’t want two people working on the same thing, unless they are collaborating. That’s why you have the assigned field. The started field is filled with the time and/or date they picked it up. The reason for this is that if they take too long, you can ask if they are stuck or need help.
As for me personally, I prefer it digitally just because I can type faster than I write. Also it’s on the screen so I don’t lose focus on what I’m doing. People’s minds tend to wander sometimes. That helps to keep me on task.
2 Likes
thanks. another thing, how specific do you usually make your assignments? like do you just say simple stuff like “make better obstacles” or “make obstacles that include spikes, do small amounts of damage, and can move that are modeled in blender”?
1 Like
The backlog is just a method to keep what needs to be done, what is being currently worked on, and what has been completed organized. I’m trained in the field so I have actual docs out of habit. But hey, whatever works for you, use it.
2 Likes
You can just make a dev discord server as this is a far more organized and scalable approach. If you’re allergic to trello, this is the better option.
1 Like
It depends on the task itself. Sometimes when I come up with a new task, it’s still in brainstorming mode so more details are needed. For something complex, try to break it down into multiple tasks. This follows the divide and conquer strategy. For your example, if it’s just me, then “make better obstacles” generally is enough. However, if it’s a team environment, more detail is better because if you add something and someone else picks it up, they will have a better understanding of what needs to be done.
One thing that I want to mention about Agile. You can find the Agile Manifesto using a Google search. I’ll give you a run down of the basics.
- Sprint: A coding session that lasts anywhere between 2 weeks and 6 weeks.
- Backlog: A To-Do list describing what needs to be done.
- Retrospect Meeting: A meeting with team members to discuss various aspects of the project.
- Scrum Master: The project manager who leads the team to a successful outcome. Interfaces between the team and management and coordinates all communications between them.
The retrospect meeting has several purposes. Some of those are to discuss and decide on what to start, what to stop, and what to keep working on. Also discussed is design and architectural changes, new features, use cases, etc… It’s basically a roundtable where everyone can voice their ideas for discussion, discuss problems and solutions, and discuss any changes that should or need to be made. This is how professional engineers do it.
There can be multiple teams. Look at Roblox itself for instance. They have multiple teams working on different aspects of their platform. They have even said so themselves through various forum posts. The scrum master is the leader of one team, so there are multiple scrum masters that can hold meetings between themselves and/or management.
EDIT:
I forgot to mention the order of things. After a sprint ends, you have the retrospect meeting, then you start another sprint. The idea is to have something ready to be delivered to the customer at the end of each sprint. So you have a product that is delivered incrementally instead of all at once. So a customer can have basic working software in 3 months instead of getting a product in 2 years with all the functionality, features, etc… That’s the whole point of Agile verses Waterfall. Everything is incremental instead of all at once.
1 Like
Could it be that you’ve focused on back-end for the last 2 years? While I usually did front end stuff when I started, I have done a lot of back end work for the past year and found it pretty difficult to make actual game features instead of just writing code to make my code better.
1 Like