game Preferences settings

[Kiwikkiwik]

Thank you for your response Mobhack.
I see, it is a game and not a simulation, and has many God problems, but I think this one has an easy fix, not requiring reworking the game.
I brought this up because from first hand accounts it seems the worst problem a soldier faces is often identifying where fire comes from.
But with the range information and the shooting graphic for direction the Soldier can easily work out where fire comes form.
Then just paste that position with artillery or Z fire roll up to it and destroy whatever it was.
This makes it impossible for a defender to play a stealthy game.
I know you know all this but I say this to explain my thinking.
So maybe just the range data can be removed from the global messages?
That would create the spotting difficulty and make the game a little less God like?
If you want to know the range then the T for Target button gives that information but only for spotted units, not unspotted as it should be?
I dont think this modest change would cause any confusion for your civilian players?

[Mobhack]

Originally Posted by Kiwikkiwik

Thank you for your response Mobhack.
I see, it is a game and not a simulation, and has many God problems, but I think this one has an easy fix, not requiring reworking the game.
I brought this up because from first hand accounts it seems the worst problem a soldier faces is often identifying where fire comes from.
But with the range information and the shooting graphic for direction the Soldier can easily work out where fire comes form.
Then just paste that position with artillery or Z fire roll up to it and destroy whatever it was.
This makes it impossible for a defender to play a stealthy game.
I know you know all this but I say this to explain my thinking.
So maybe just the range data can be removed from the global messages?
That would create the spotting difficulty and make the game a little less God like?
If you want to know the range then the T for Target button gives that information but only for spotted units, not unspotted as it should be?
I dont think this modest change would cause any confusion for your civilian players?

The changes you are suggesting would require a brand new game, unfortunately. The messaging system is core game code, and is fundamental to the operation of PBEM replay for one thing. Not "modest" at all I am afraid.

[Kiwikkiwik]

Im not sure if I was clear enough before,
I think that in computer talk we are dealing with a string?
So when the string is built isn't it easy to not put the range info in?
The change would be something like
muyunitnamevariable + " firing at " + opponentsunitsnamevariable + carriagereturn + "Range " + rangevariable + " metres"
to
muyunitnamevariable + " firing at " + opponentsunitsnakevariable
So just dont call the global rangevariable when building the string, wherever else the Global rangevariable is used is unaffected.
This truncated message can then be passed around, stored, discarded or displayed just like the origional is?

[Imp]

Originally Posted by Kiwikkiwik

Im not sure if I was clear enough before,
I think that in computer talk we are dealing with a string?
So when the string is built isn't it easy to not put the range info in?
The change would be something like
muyunitnamevariable + " firing at " + opponentsunitsnamevariable + carriagereturn + "Range " + rangevariable + " metres"
to
muyunitnamevariable + " firing at " + opponentsunitsnakevariable
So just dont call the global rangevariable when building the string, wherever else the Global rangevariable is used is unaffected.
This truncated message can then be passed around, stored, discarded or displayed just like the origional is?

Try playing with the hex grid off the game looks far better & you have to judge ranges, I put them on sometimes if close fighting is happening for example in woods