Modding Writing Tip #2

 Modding Writing Tips #2

Hello ladies and gents! The last tips was focus on modding a [Hard] Difficulty, but what if you struggle with wording?

One of the biggest struggles that most Modders and Mappers face in the community is miscommunication of ideas and it not translating well on paper.

This can mean a lot of things going as far as not understanding a mapper style well enough to conceive a meaningful post or as small as having basic suggestions without it having the detail to explain what it is the mapper needs.

That's why good wording is important more than ever, especially when diving against multiple different cultures in the scene.

English is the main language for modding, but majority of others have notable language barrier, and it's very easy to sound very rude or vey nonchalant when trying to remain Neutral, due to the complexity of languages and communication.

SO HOW DO I DEAL WITH IT?

In the case you are on the side of mapping where wording is a problem, no worries i'm here to help!

Sometimes all it takes is to substitute a word instead to make your mod brighter and more positive to the mapper!

Example:

The issue with the wording here is mainly on the word "Random". 

Random can sound very hurtful to a lot of individuals since people take a lot of delicate time in to mapping. While you may think it's random, the mapper may disagree.

It's always important to take the mapper's perspective first before your own, as your goal is to improve the mapper's idea, not change them.

Other instances is questioning the mapper's ideas.

Example:

The issue with this question is that while you may not have no ill intent, but it can easily be seen as offensive because it make it seems like your suggestion is better than the mapper's idea and it can appear as snarky.

This can apply to any type of question in similar matter such as "Why did you do this?" "Is there any there reason why you did this instead of this?" type of questions

Not to say you cannot ask the mapper any questions, but just try to keep in mind of how that would sound on paper especially as we speak about language barrier and other aspects that can lead to unnecessary misunderstandings.

There is another thing to be concern about such as vague wording. vague wording can be highly problematic when especially when talking to new mappers, as often times it doesn't open enough of a reason as to why you suggest something.

Example: 

Like while there may be some logic into mod if looked through the editor but what it is missing, is the missing why?

Ask yourself as the modder, "Why do I want them to change this?", "Does my reason goes against mapper intentions?" and "Do my reason improves the maps?"

If those questions start to cast doubt in your mind, try to focus more on other things surrounding the map until your more comfortable or confident in your decision. It's good to apply more thinking into the mods before having them on the threads.

That will be all the tips for today. Thanks for anyone who taken a chance to read this.