If it’s fictional, I’ll write a paragraph or two, only one or two pictures as well. If it’s some kind of replica, I’ll take the first paragraph from the wiki and link the full site and put it at the end. I try not to be excessive with my descriptions.

I do think the copy paste from wikipedia is too much, you can just link people there
But for fictional builds, backstory is nice to have

My biggest pet peeve is when someone doesn’t use the same formatting in their forum posts.

is taking the photos plagiarism? your not really gaining anything like money? i always like to get my photos from museums so i can at least credit someone.

@sheepsblood
"@ Madness trust me i dont"
then why do you care?

no such thing as too much info

Depends. As a RL pilot with more than 4,000 hours of actual flight time, I like the builder to relay all functionalities, including all AGs. Power settings and takeoff/landing/maneuvering speeds are good to know, as well as any built-in limitations and flying peculiarities. The player doesn’t have to read them if they don’t want to, so what’s the heartburn? I have fairly long descriptions as I attempt to imbue my builds with many of the RL flight characteristics and I like to make sure the player knows what they need to know to not get frustrated. As a result, complex builds tend to have long descriptions. Simple builds, on the other hand, might not have a long description. But there is a time and place for both long and short descriptions, as appropriate.

I have found that extra info is actually appreciated, as long as you leave it as a link to a separate forum post. A few of my followers (more than I expect) actually take the time to read my long stuff, which is quite nice. Though my long-form content, when it gets more technical, is really just for me to build up my little portfolio that I have made here :)
.
To be fair, a pasted Wikipedia entry doesn’t really add much. I suppose my long descriptions are different in that they essentially say “hey, I can do math!”.

Quite sad that people only care about giving the upvote and not about the build itself

Like, I don’t really care about when the mig15 served, I just want to upvote it, please let me do that

I don't think your forum is any different than what yer complaining about

No

I do enjoy writing a fictional history for a build to give it character, but I don’t really put any images in the description for a build. I make sure to show off the build in the plane’s thumbnail and screenshots there.
.
Also, I make sure the controls are normally the things listed first.

@asteroidbook345 - Exactly!
@Chancey21 - Wonderful idea!
@Mage2IsTriggered - Good point, a format should be decided upon. Maybe even a user script so those items can be added. Not just a blank area which we have to blindly develop our own formats.
@KnightOfRen - Chaos is the precursor to organization and harmony. Therefore we are headed towards people doing what they want but, in a formatted manner> This will make it easier on the other participants to understand and absorb the creators work.

T

But long descriptions are thorough and necessary, especially on builds fictional to our own.

If it's a fictional one I can understand a Wiki. If it's something like a MiG-15 that's super basic your description doesn't need to be that long.

Personally, i really dont give a damn, in fact, i like having long text descriptions, as long as they are well organized.

Just leave a link to more info for those interested

I agree. If I want to upvote it, I shouldn’t have to grab the scroll bar and get there

let people do what they want...
I have spoken

@Astro12
See, that is beautiful. It has a format. I think we should all follow a format. Also, limit our content to a few examples. While everyone gets to do whatever they want because that is the beauty of each persons personality. We could still do it in a formatted manner. So it is easier to follow, making things less frustrating in the end.

@UsualPioneer
2020 27" iMac 3.8Ghz 8 Core i7
40GB DDR4
1TB internal SSD & 2 TB external SSD
AMD Radeon Pro 5700 XT 16 GB

I had been saving for this one for awhile. My last iMac was a mid-2011. I handed that one over to a friend. I did make some upgrades to it. SSD drive and of course maxed memory.

@UsualPioneer
I said the plagiarism comment just to make my point more clear about pointless added content.
I didn't start this post out of thin air. I have been sitting on it for a long while.
This is the straw that broke the camels back.
https://www.simpleplanes.com/a/F62PhI/Boeing-747-300-Mahan-Air
Not the written description, it was the obsessive photos that did it.
I did upvote and made a snarky but nice comment. So I am not that much of a dick. That is why I cam here to voice my opinion.
Luckily, I got you to respond. You are a great person for allowing me to vent.

My standard description format :
- Title (where without the title)
- Type (to understand what the build is)
- Short description (explains a little bit more about what it is)
- History [if fictional]
- Controls (logical I think)
- Armament [if any](very important for a military plane)
- Maximum speed (to have an impression)
- Notes (what to pay attention to, e.g. peculiarities of the flight or triggering of some mechanisms)
- Features (what has been worked on and what can be looked at)
- Credits (thank those who helped or tried to help)
- Bonus moment [sometimes] (just an interesting screenshot at the end)

I try to give information briefly and to the point. I understand that no one will be interested in reading a wall of text, so I try to format and add screenshots.