New Player Tips

From VGA Planets Wiki
Revision as of 20:43, 27 October 2014 by LordLancelot (talk | contribs) (Created page with "==orymus en za'er == For newcomers to stay, they need either to win, or understand why they've lost. In other words, they cannot lose without understanding why. So why are ne...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

orymus en za'er

For newcomers to stay, they need either to win, or understand why they've lost. In other words, they cannot lose without understanding why.

So why are newcomers losing? My theories, and how they can be used:

1 - Ship Construction / Customization Let's face it, we're dealing with a ship system that has a very strong impact on a player's economy.

1a - Torps While most of us have read Donovan's supersite or have calculated things on our own, we all are well aware there are only really 4 types of torps. They each serve a purpose, and this is something we've learned early on and is an integral part of our strategy. Why not let newcomers in on the secret? Highlight these 4 in the lists, and add a short descriptive text in some shiny color so people understand: "Gamma is used only to capture ships and does little to blast these shields off!" "mk4 is a good bang for your bucks!" "mk7 is your all-purpose torp!" "mk8 is costly as hell, use only when you know what you're doing!"

1b - Beams Beams are a bit less straightforward, but there are constants: Disruptors and x-rays are good for capturing, blasters are good to fight, etc. Highlight them and give a descriptive text as to why each one is good.

1c - Engines Most ships should have Transwarps. It is a shame there are so many engines when so little are actually useful, but it is part of the game, and part of the learning curve. But if you want newcomers to stay, they can't fall prey to the "I'll build whatever I can afford". A ship with Level 3 engines may be an Eros, not an LCC. Perhaps highlight the Transwaps, consider them standard, and mark the others as iffy. Add a prompt the first time a player builds a ship and selects a different drive.

1d - Hulls That's a lot more complex. But most hulls have their own hidden agenda, and we all know why we like our ships. A series of numbers (cargo size, fuel tanks, beams, etc.) gives us all the info we need, but to newcomers, it is hard to tell ships apart. Let them have it easy! Give some descriptive comments about each hull: Nebula? sweet cargo, all-purpose ship, can help you lay mines, etc. LCC? Remember, you are a Lizard, your ground force is strong... maybe that cargo can be used for something else than carrying minerals? etc.


2 - Early game Economy We all have our own agenda, but generally it involves spreading to a bunch of new worlds fast (I'm looking at you Borg!) and remain undetected. Players understand the need to colonize, but they don't understand it really. They don't tend to have a good understanding of what resources they'll be lacking first and why. As a result, they don't really know how to determine what worlds they should conquer first. Similarly, they don't understand the need to stay hidden, and quite frankly, they may not know that being in orbit means you are hidden from other players for the most part.

Single player missions help them figure some of that out, and prevents them from miserably failing on their first game, but perhaps the above needs to be experimented a bit more with during the first single player mission or companion tutorial?

3 - Each game is different... We have mentors vs midshipmen. That's great as this will provide them with good feedback. But what about other games? Wouldn't it be our duty to tell the novice players we defeat why they were defeated? It would show our sportsmanship than to teach them how to get better. If you are like me, you certainly don't appreciate squishing weaker opponents when you know they don't stand a chance, correct? I often refrain from striking down a weak opponent early game because I feel that would be a cheap shot (putting me in difficult situations sometimes). Probably some of you already do so without realizing the value of this, but telling players why they fail is critical. It is what helps people stand back up and try to find a solution instead of just going away. Get rid of your pride: everyone knows you are a good player, you know it. No need to tell them you were simply better. In most situations, your opponents have made critical mistakes: it doesn't hurt your pride to point them out gently and suggest solutions or alternatives you would've chosen yourself.

All of these are low hanging fruits; simple modifications to the system that should be invisible to us, but give newcomers a fighting chance to do better on their very first game. Perhaps this will create a new problem (players sticking to what is written and forgetting to look at the numbers and think outside the box) but that will at least have moved the problem further along the learning curve.