Jump to content

EViL0nE

Members
  • Posts

    10
  • Joined

  • Last visited

Posts posted by EViL0nE

  1. Espionage is an attack and it is antithesis to the entire concept of beige "a chance to rebuild after losing war[s]" - If your military units are can be destroyed while in beige. . . you're not providing the chance to rebuild. Spies are military units as well. 

    1. A nation on beige should be able to gather intel from anyone, and should be able to perform all spy operations against nations they are currently at war with.

    2. A nation on beige should be vulnerable to gather intel by anyone, and should be vulnerable to all spy operations from nations they are currently at war with.

    • Upvote 2
  2. 1 hour ago, hidude45454 said:

    In all seriousness, what's wrong with hiring mercenaries?

    I'm honored that TFP is scare enough of us mostly-retired barely-awake Farkers that they had to hire mercenaries. It makes me feel so good I might not have to take my evening Metamucil.

    • Haha 1
    • Upvote 2
  3. 1 hour ago, Zephyr said:

    I'm aware that at current a nation can always spy a nation they're at war with, but it's unclear to me what Bozzie's intentions were and what assumptions the rest of us are making about how this would/should be implemented.

    I don't think I'd like this change if it means that even nations at war cannot spy each other as that seems unfair to those actively fighting. Then I'm thinking if warring nations can still spy each other, then there's not much difference if your opponents are beige cycling you. I guess this change could be useful if you're losing the conventional war but winning the spy game, but then maybe that actually just means this mechanic hampers your opportunity to use your best assets most effectively...unless nations on beige can still spy? Though that again doesn't seem fair, you can neither conventionally retaliate if spied by beiged nations, or spy them back. If they're sitting on a juicy beige timer too, it'd be even more frustrating to have no options to respond with. This would seem to then make beige even more valuable to the detriment of the victorious side, becoming even more reason to deny opponents beige time and exacerbate that "problem".

    I guess I'm not sure if this change would matter or if it'd actually be good for the conventionally disadvantaged side, in both their immediate ability to exploit those mechanics and the influence it has on opponent willingness to beige. *shrug*

    Well, for instance, I have spent about 9 days in beige over the last few weeks with 0 active wars. In that time I have been unable to rebuild spies or nukes and have to constantly rebuy tanks as they are spied away. With 0 active wars while on beige. This is clearly at odds with the concept of beige being a place of rest and rebuild. 

    I don't fault my opponents for using the tactic. It allows a win in the early round(s) of a war to steamroll into a significantly more resounding win. If your opponents can be stopped from fully rebuilding with nothing more than a few million in spy ops every day, with the added bonus of forcing them to blow steel on tank rebuying, that's a heck of a lot cheaper than actually fighting a war. With an overwhelming nation count and the current beige/spy mechanic, there's no reason to not beige the nations. They either sit in beige and gain little, or come out and continue getting piled on.

  4. 11 hours ago, Indger said:

    I dont support this
     

    Care to expand on your reasoning, from a game-mechanics and logic perspective? 

     

    Or is your reply specifically "currently we're benefitting from the current mechanic so don't change it while we're benefitting from it" ?

  5. Then everyone will have to merge for that to work. The way the formula works, treasures' effect on the color stock is capped at 10% before being reduced by each qualifying alliance minus one. A color can have all the treasures in the world, but it will get 0% stock bonus if there are 21 alliances on that one color. Right now there are 44 qualifying alliances.

     

    Ah, you're right.  I just looked at the formula and didn't see the MIN was [0].1 and not 1.

  6. I'm no DBA.. but I think if 99,999.99 is a limit based on storage/performance, you're using the wrong data type

     

    MySQL's documentation is a black hole when you get into this stuff, but as I understand it, a decimal type (my guess of what you're using, if you're using VARCHAR or similar, there's no help for you) stores 99,999.99 in 4 bytes (3 bytes for the 99,999 and 1 for the .99).

    If you really like type decimal, you have the same storage requirements by going to a limit of 999,999.99.

     

    Since we're only using positive values for resource storage, you would get better storage efficiancy and performance by using an unsigned mediumint which would up the maximum to 167,772.15 in only 3 bytes (formatting of the decimal would be done for display only).  If you moved to an unsigned int, your maximum would be 42,949,672.95 in 4 bytes.

     

    This would increase performance, storage efficiency and better prepare the game for the long-haul.  You may think 99,999 steel in a single nation is unfathomable, but wait until you have nations that are 7+ years old... 

     

    I'm sure there are people playing who are far more knowledgeable of sql optimization who could chime in and affirm/correct my understanding.

    • Upvote 1
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and the Guidelines of the game and community.