- Subscribers:
- Visitors:
- Players:
Community Feedback
We're listening. For players who wish to have a voice in the future of Evernight, this is the place to talk to management. This is the newsgroup we'll be actively monitoring on a daily basis.
Unstoppable 10k Games
Submitted by ducky004 8/4/2013 2:44:00 PM {time} ago in Community Feedback
Admittedly I may be wrong about this, but I don't think so and wanted to check. The description for the game states that "the mountain BB will be set to 4,000 fury on tick 25". Now, I can't accurately recall how the tick/cycle process works, but I assume that if the mountain BB isn't 4,000 fury until tick 25, shouldn't the earliest it be able to be cast be cycle 25, thus ending a game(if its the 6th bb) on cycle 26? Ducky
I agree, the game description does leave too much room for ambiguity.
"at tick 25" could reasonably be interpreted differently by different players.
The game description should be changed to indicate the Cycle# rather than Tick# for better clarity.
-------Original Message-------
ducky004 wrote: Admittedly I may be wrong about this, but I don't think so and wanted to check.
The description for the game states that "the mountain BB will be set to 4,000 fury on tick 25".
Now, I can't accurately recall how the tick/cycle process works, but I assume that if the mountain BB isn't 4,000 fury until tick 25, shouldn't the earliest it be able to be cast be cycle 25, thus ending a game(if its the 6th bb) on cycle 26?
Ducky
Even then, 'at tick 25' should not mean that the spell cost is lowered and able to be cast on cycle 24.
I can see that you understand my meaning though...just a bit upset that it cost me a win :/
Ducky
-------Original Message-------
Temptations wrote:
I agree, the game description does leave too much room for ambiguity.
"at tick 25" could reasonably be interpreted differently by different players.
The game description should be changed to indicate the Cycle# rather than Tick# for better clarity.
-------Original Message-------
ducky004 wrote: Admittedly I may be wrong about this, but I don't think so and wanted to check.
The description for the game states that "the mountain BB will be set to 4,000 fury on tick 25".
Now, I can't accurately recall how the tick/cycle process works, but I assume that if the mountain BB isn't 4,000 fury until tick 25, shouldn't the earliest it be able to be cast be cycle 25, thus ending a game(if its the 6th bb) on cycle 26?
Ducky
I see what you saying.
In my mind, they way I would interpret "at tick 25" would tend to agree with your assessment. It should not have been possible to cast during cycle 24.
The problem though isn't just a matter of interpretation. It also perceptions of the definitions of the the terms Turn/Tick/Cycle.
In my mind, the term "tick" refers specifically and exclusively to the discrete few seconds a game is offline, its orders are being processed and upon completion the cycle number is incremented.
As in the phrase, "The game is ticking." Thus, the term "tick"
However many players use all three terms more or less interchangeably. Thus introducing a boatload of potential miscommunication issues. Most usually brought to the surface as the result of a nap dissolution.
I interpret "at tick 25" to refer to "the 25th tick" which if you're counting ticks is the tick that happens between the Citadel indicating Cycle 25 & Cycle 26.
The "tick" that advanced the Citadel from Cycle 24 to Cycle 25 was the 24th time the game "ticked."
At least that is how *I* interpret the terms in my mind.
The bottom line though is, the game description needs to be fixed to something very clear and completely unambiguous.
Such as:
"Players will be able to cast Mountain BB for 4,000F starting cycle XX."
Meaning when the citadel indicates XX, it's available for casting at 4,000F.
-------Original Message-------
ducky004 wrote: Even then, 'at tick 25' should not mean that the spell cost is lowered and able to be cast on cycle 24.
I can see that you understand my meaning though...just a bit upset that it cost me a win :/
Ducky
-------Original Message-------
Temptations wrote:
I agree, the game description does leave too much room for ambiguity.
"at tick 25" could reasonably be interpreted differently by different players.
The game description should be changed to indicate the Cycle# rather than Tick# for better clarity.
-------Original Message-------
ducky004 wrote: Admittedly I may be wrong about this, but I don't think so and wanted to check.
The description for the game states that "the mountain BB will be set to 4,000 fury on tick 25".
Now, I can't accurately recall how the tick/cycle process works, but I assume that if the mountain BB isn't 4,000 fury until tick 25, shouldn't the earliest it be able to be cast be cycle 25, thus ending a game(if its the 6th bb) on cycle 26?
Ducky
Seems like we interpret it the same then. I also consider the time in between cycles as the "tick". Hence my thinking that the mountain BB would not be able to be cast until cycle 25, with the 25th tick being between cycles 24 & 25. As you said ;)
I do agree with your proposed solution though as it should clear any possible confusion up.
Sucks being the guinea pig at times...even if it is a role I have gladly taken in the past for my own purposes :p
Ducky
-------Original Message-------
Temptations wrote:
I see what you saying.
In my mind, they way I would interpret "at tick 25" would tend to agree with your assessment. It should not have been possible to cast during cycle 24.
The problem though isn't just a matter of interpretation. It also perceptions of the definitions of the the terms Turn/Tick/Cycle.
In my mind, the term "tick" refers specifically and exclusively to the discrete few seconds a game is offline, its orders are being processed and upon completion the cycle number is incremented.
As in the phrase, "The game is ticking." Thus, the term "tick"
However many players use all three terms more or less interchangeably. Thus introducing a boatload of potential miscommunication issues. Most usually brought to the surface as the result of a nap dissolution.
I interpret "at tick 25" to refer to "the 25th tick" which if you're counting ticks is the tick that happens between the Citadel indicating Cycle 25 & Cycle 26.
The "tick" that advanced the Citadel from Cycle 24 to Cycle 25 was the 24th time the game "ticked."
At least that is how *I* interpret the terms in my mind.
The bottom line though is, the game description needs to be fixed to something very clear and completely unambiguous.
Such as:
"Players will be able to cast Mountain BB for 4,000F starting cycle XX."
Meaning when the citadel indicates XX, it's available for casting at 4,000F.
-------Original Message-------
ducky004 wrote: Even then, 'at tick 25' should not mean that the spell cost is lowered and able to be cast on cycle 24.
I can see that you understand my meaning though...just a bit upset that it cost me a win :/
Ducky
-------Original Message-------
Temptations wrote:
I agree, the game description does leave too much room for ambiguity.
"at tick 25" could reasonably be interpreted differently by different players.
The game description should be changed to indicate the Cycle# rather than Tick# for better clarity.
-------Original Message-------
ducky004 wrote: Admittedly I may be wrong about this, but I don't think so and wanted to check.
The description for the game states that "the mountain BB will be set to 4,000 fury on tick 25".
Now, I can't accurately recall how the tick/cycle process works, but I assume that if the mountain BB isn't 4,000 fury until tick 25, shouldn't the earliest it be able to be cast be cycle 25, thus ending a game(if its the 6th bb) on cycle 26?
Ducky
Connect With Us