That’s something! I just don’t want people to drag out a square with no code, publish the project, and then claim the prize.
ah, ok makes sense
- liked ten posts
I have done text formatting in these posts
Finally @MegaSCamp - So sorry about the delay, but here are some more tips related to trail art!
Today we are covering: Curves, and some tips for simplifying your trail art code (as a bonus)
I use curves in pretty much all my Hopscotch trail art projects. Most of the objects in the real world are at least a little smooth in the edges. Today, I’m sharing my tips on how to do successful curves. Keep in mind that the trail art code that I am using for curves is simple, and there’s probably some faster way to do it. I have used this method for over a year now though, and I find it a great balance between speed and simplicity.
The basic idea is that to create a smooth turn (which is what a curve is), we draw a trail for a short distance, then turn a little bit, and repeat until we reach the target angle. I usually use this code, which is easily changeable:
repeat times(The angle you want the finished curve to have turned with / 10) draw a trail color(any color) width(any width) move forward(any move forward value, see below for tips) turn(10) degrees - see below for more info end repeat
If you read my concept explanation above, you probably realize what all these blocks do. I’ll just like to explain some of the values:
move forward - I usually put a value between 1-5, if I turn by 10 degrees every time. 1 is a super slight curve that is hardly noticeable if you have a width that’s bigger than 10-15. 5 is a pretty big curve - I’ve used it for iPhone trail art recreations in the past.
turn degrees - I have put 10 degrees as a static value in my example, because that is what I’m using the most. However, as long as you make sure to match this value with that the total curve angle is being divided with in the repeat times-bubble, you can put any value here. I usually put 5 or 9 if I’m not using 10 (9 because I can do Repeat Times 10 and get a 90-degree turn)
My curve has jagged edges! What should I do?
This problem happens to me every now and then, and it is because you move forward to much, and turn too little to compensate. Some solutions:
- Decrease the amount you turn with and divide the current move forward value with the same ratio that you decreased the turn block with (I usually divide both by two compared to what they were before when the line was jagged)
- Increase the trail width if you can (but this makes the lines thicker, so it may not be optimal)
- If the jagged edges are hardly noticeable, you can skip changing the code so you don’t have to compromise on the speed.
A tip when you’re reusing the same curve multiple times - put it in a rainbow custom block! That really helps to keep track of everything.
Need to see projects using my curve code? Open pretty much any of my trail art project, and look in all the rainbow blocks named “Curve” (they may have a number after them), and you’ll find lots of examples on how the same piece of code can fit in many different projects!
I’ll step up my game and get more of these tutorials out in a shorter period of time - but time really flies! Before we end this lesson though, I’ll like to share some quick tips on how to keep your code organized - something which I am technically good at, but when doing daily projects, I do choose quantity before organization. I’m sorry if any of you look at some of my projects and find the code and editor badly organized - you can always ask me if you have any questions. Nevermind, on to the tips!
Tips for keeping your code organized
Use custom blocks and rainbow rules as much as possible This really helps. If you are reusing the same piece of code over and over again, your best bet is to create a custom block for it. You often have to fine-tune trail art (I’ll probably provide my tips for that later on as well), and if you have to change a piece of code that you have reused with a custom block, you just have to do the changes one time to that custom block.
Even if you’re not reusing your code, you can always put it inside a custom block with a title that makes it easy for you to understand what part in the code that is related to each other, and what it does.
If possible, use clones or multiple objects It’s always cool to do fast trail arts. Therefore, you might want to execute code in parallel. If you haven’t worked with using clones to do things in parallel with your regular code, you can use multiple objects instead, or give the clone-method a go. It’s not actually that difficult - you create clones of the original object, and then put the trail art code that you’d normally would have put in a new object inside it’s one (If clone index = a unique number larger than 2 and smaller than the amount of clones that you have created +1) Use wait-blocks for adjusting the timing, and make sure to…
Name your objects Naming your objects really help to understand what they’re doing, as many trail art projects only include blank text objects.
Use the object view to scroll between objects To avoid editing and the wrong object and to increase development speed.
I hope you like these tips!
Next theme: not decided yet, reply if you have any suggestions!
awesome help as per usual will, thank you so so much!
curves yes thanks for making this
Thanks will, ur the best
Thanks for the kind comments y’all, I’m glad that you are enjoying this!
Someone said y’all again, I don’t like people saying y’all, too much slang…
Hi people - sorry for not checking in on your for over a week! I have worked on some things behind the scenes and other things on Hopscotch, and haven’t really had the time to write something particularly long.
Let me share my plan for the upcoming weeks, since school starts officially for me again in exactly 17 days.
- Get out a few more trail art tutorials, independent of camp activities.
- Host one competition that’s short/mid-long
- Do another one of the checklist challenges
- Compile results for earlier challenges and after that decide teams and certain advantages for previous winners in an exciting final collab challenge! This will be done after the summer contest judging results are out.
- Collect feedback from all of you related to the camp.
- Close the camp for this year somewhere around 2020-08-23T22:00:00Z.
I can already get back on the Host one competition that’s short/mid-long-point!
First, I’d like to clarify that results from previous challenges will be calculated and announced when the last, final collab challenge is set up. You’ll get more information when it’s approaching.
And now, to a challenge I think is pretty unique!
The Neon Challenge!
For this challenge, you must create a project that is focused around neon colors! Other than that, it can be anything - a game, a trail art, a coded website, music - you name it! BUT, there is a bit of a twist to it. You all have to include an individually assigned neon color in at least one place your project.
Like all challenges, this challenge is also optional - enter if you can! Even though it’s optional, I have assigned a neon color code for every user in Mega Summer Camp this year (referring to the members in the MegaSCamp group). Look below for YOUR assigned neon color code!
Entries in the neon challenge are due 2020-08-04T17:00:00Z.
The top 3 people of this challenge will receive likes, a shoutout in one of my projects, and a special prize related to the final collab competition! If you can not/don’t want to compete in that, I’ll turn the prize into something else.
Assigned color codes
Open this folder
List of assigned color codes - click on the supplied link for an instant conversion to other color code formats! The list is alphabetically ordered.
The list has been generated via a simple program I wrote in Python. I also visualized every color to make sure everyone got a fair color. Some of you have similar colors, but every color has been generated randomly. If you can’t see your name on the assigned color codes list, ask and I’ll fix it.
Nice. I’ll try to make something.
Some of the colors aren’t very neon-y tho haha, cuz neons are usually super bold and bright. Mine’s almost pastel-y. If you ever think about redoing these, or randomly generating neons in the future, I’d probably limit the saturation range to 70-100. Another small thing about that - S and B both go to 100, not 360, btw. For some reason, a lot of the saturations you have listed are going up to 360? It doesn’t make much of a difference unless you’re converting it.
aah really like the sound of this challenge- gonna go check out the colour now!
Too bad I left, I wish I stayed. this is a cool challenge!
Do you want HSB(88,37,100) or HSB(88,100,100)?
S 137 would translate to 36, not 37
I love my color ^^
Mines not exactly neon…
Cool challenge! I’ll try to do something for it.
@William04GamerA even thought I’m not part of the camp anymore could I still have a color for this challenge so I can make a non camp project involving this?