@blt it is good since unlike me, you actually bother to hook players into reading the description, and make it interesting for random people to read xdd
It's just a different style. I don't see anything wrong in the description
@blt there is no link in the comment?
.
The format has 2 parts, the user manual (controls and build information) and the information (lore).
.
Sections in the user manual are entered using the priority of: credits, controls, other, dev notes (self-reflection type content)
@hpgbproductions old woman i have question
how do i do it for uhhh this
(please don’t reply on post, imma try to keep it untainted but your name will be put down at the shoutouts…along the lines of ***Thanks to [User](Profile link) for
helping me format*** then do a @…
This is because i like your style of formatting the descriptions.
Captivating is nice but most people just wanna know how it works, so clearly list the controls first. If you used any activation groups, list them and what they do. If you have sliders, explain what they're for. If it's a car, explain if you use roll, or yaw to steer.
If you really want to impress people, test your plane enough to know how to land it, and how fast you should do it. List the stall speed (the slowest speed the plane can fly and maintain altitude).
Is there anything dangerous? Does the plane do weird things if you try to roll and pitch at the same time? Is there a cruising speed where the plane will fly straight without gaining or losing altitude?
That kind of stuff goes first. At the bare minimum, at least list what 'AG's you have and what they do
After that you can make up a backstory (if its a fictional plane) or write about its history. Why was it made, what was its job, did it do anything important, etc.
Pictures are a good idea, both of the real thing but especially screenshots of the thing flying. A good screenshot does a great job of stoking peoples imagination and really sets it apart from the plain black background in the builder.
Include information and maybe a story, and of course controls.
I use a wikipedia-ish description for the most part, where production and uses information is given
@hpgbproductions ohh thanks haha
@blt it is good since unlike me, you actually bother to hook players into reading the description, and make it interesting for random people to read xdd
It's just a different style. I don't see anything wrong in the description
@hpgbproductions okai thanks oldie
look at my latest post btw
@blt there is no link in the comment?
.
The format has 2 parts, the user manual (controls and build information) and the information (lore).
.
Sections in the user manual are entered using the priority of: credits, controls, other, dev notes (self-reflection type content)
@hpgbproductions old woman i have question
how do i do it for uhhh this
(please don’t reply on post, imma try to keep it untainted but your name will be put down at the shoutouts…along the lines of
***Thanks to [User](Profile link) forthen do a @…helping me format***
This is because i like your style of formatting the descriptions.
Captivating is nice but most people just wanna know how it works, so clearly list the controls first. If you used any activation groups, list them and what they do. If you have sliders, explain what they're for. If it's a car, explain if you use roll, or yaw to steer.
If you really want to impress people, test your plane enough to know how to land it, and how fast you should do it. List the stall speed (the slowest speed the plane can fly and maintain altitude).
Is there anything dangerous? Does the plane do weird things if you try to roll and pitch at the same time? Is there a cruising speed where the plane will fly straight without gaining or losing altitude?
That kind of stuff goes first. At the bare minimum, at least list what 'AG's you have and what they do
After that you can make up a backstory (if its a fictional plane) or write about its history. Why was it made, what was its job, did it do anything important, etc.
Pictures are a good idea, both of the real thing but especially screenshots of the thing flying. A good screenshot does a great job of stoking peoples imagination and really sets it apart from the plain black background in the builder.
Thank you. @AstleyIndustries
Include information and maybe a story, and of course controls.
I use a wikipedia-ish description for the most part, where production and uses information is given