Jump to content
Naval Games Community

Recommended Posts

Posted

I realpy liked @Hethwill approach. Looking through all this posts only he ia focusing on possible improvement and not on picking up flaws. Solution to a problem within this post is simple:

Using @admin guide let's agree to a format how we will provide feedback or suggestion. Very common wirhin businesses is STAR format which you can read about which can be modified and accomodated to our needs and agreed with developers team. 

Quick sticky topic with suggestion rules.Whichever suggestion doea not follow above format will be discarded and not taken into account. All others developer team will provide a feedback on following with decision and closure of the topic.

It is all about agreement between both sides what is a format and following it as we all have common goal to make game successful. 

  • Like 1
Posted
6 hours ago, admin said:

In this case community does not know what to talk about and start adding new things into the subject NOT ONLY making the topic about chainshot impossible to read BUT ALSO losing the suggestion on lighthouses. 

This is incorrect imo or at least only partially true. I think you are referring to the repairs that people keep bringing up in chain topic. Some unbalanced, bad mechanics or design choices can lead to other things becoming unbalanced or even game breaking. It can be like a chain reaction :) 1 bad thing leads to another. There are certain Topics like duel rooms patrol ROEs, multi repairs, fireships and other things you like to avoid.

Posted
21 hours ago, victor said:

As usual. You are right we are wrong.

 

 

This is an attitude of a hater. Are you sure you want to go this way?

We are one community. There are no us and them.

If we invest time into our posts you must too, and vice versa - if you invest time into your proposal we will consider faster or add to our useful feedback lists. If a post is unreadable and is all over the place or partially offtopic - it wastes everyone's time.

21 hours ago, victor said:

It's not true.

Since Game labs is the developer of the game, also the game design (and not only the algorithm definition/implementation and the encoding) it's up to Game Labs.

This means that it's up to Game Labs taking a potentially good game idea and develop into an actual game content.

What it seems from the last post of the admin is that he wants that players make (an important part of) the game design work instead of the developer.

 

I think you imagined some exaggerated expectations and unrealistic rules and are trying to apply them to other members of the community.


We are working on our priorities - if you want us to change the priorities - invest some time into your posts, build on others ideas and use all previous feedback on the subject you are talking about. 

 

We like to always manage expectations and here is the reply to everyone. Regarding post acknowledgement.

  • We are game developers not psychologists who are paid to talk to you.
  • The contract is - we make the game, you play the game. There was never an explicit promise that we will reply to every post, every message, every notification. We read as much as we could but we must also work.
  • When we need feedback on a particular subject - we actually post a question that is relevant for us. If you want us to acknowledge things that are not even on the priority list - this is unrealistic expectation and you should never expect answer on lighthouses when the only thing we are thinking about is chainshot and ui.
    • Here is an example of us asking for feedback and acknowledging it 
  • We respond to community feedback. Not your feedback, unless its really good. But even if it is good it might not get acknowledged.
  • If you want your feedback to get noticed by the community. MAKE IT GOOD.
  • If your feedback is not picked up by the community it might still be picked up by us - but you have to make it good and visual, its not "design work" as you try to name it. Its just how feedback should be

 

I hope all is clear now @Gregory Rainsborough?

We will post a guideline on giving feedback soon.

 

  • Like 5
Posted
7 hours ago, admin said:

This is an attitude of a hater. Are you sure you want to go this way?

We are one community. There are no us and them.

If we invest time into our posts you must too, and vice versa - if you invest time into your proposal we will consider faster or add to our useful feedback lists. If a post is unreadable and is all over the place or partially offtopic - it wastes everyone's time.

I think you imagined some exaggerated expectations and unrealistic rules and are trying to apply them to other members of the community.


We are working on our priorities - if you want us to change the priorities - invest some time into your posts, build on others ideas and use all previous feedback on the subject you are talking about. 

 

We like to always manage expectations and here is the reply to everyone. Regarding post acknowledgement.

  • We are game developers not psychologists who are paid to talk to you.
  • The contract is - we make the game, you play the game. There was never an explicit promise that we will reply to every post, every message, every notification. We read as much as we could but we must also work.
  • When we need feedback on a particular subject - we actually post a question that is relevant for us. If you want us to acknowledge things that are not even on the priority list - this is unrealistic expectation and you should never expect answer on lighthouses when the only thing we are thinking about is chainshot and ui.
    • Here is an example of us asking for feedback and acknowledging it 
  • We respond to community feedback. Not your feedback, unless its really good. But even if it is good it might not get acknowledged.
  • If you want your feedback to get noticed by the community. MAKE IT GOOD.
  • If your feedback is not picked up by the community it might still be picked up by us - but you have to make it good and visual, its not "design work" as you try to name it. Its just how feedback should be

 

I hope all is clear now @Gregory Rainsborough?

We will post a guideline on giving feedback soon.

 

I think it'd be nice to have a guideline on feedback/suggestion rules as @admin puts it, not only would it make for less crap the devs have to sift through but it would, while not guaranteeing our posts will be read, would instead make it more likely that suggestions that obey the guidelines would be seen, hopefully this is put in place sometime soon.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...