View Poll Results: What do you think of the 24 hour cool down instead of 72 hours?

Voters
858. You may not vote on this poll
  • I like it better than 72 hours.

    276 32.17%
  • I do not like the reduction of hours.

    79 9.21%
  • I'd prefer a cap on how many alliances I can join in a 72 hour period

    503 58.62%
Page 33 of 36 FirstFirst ... 233132333435 ... LastLast
Results 321 to 330 of 357

Thread: Developer Chat: Reducing Alliance Rejoin Cool Down

  1. #321

    Default

    Quote Originally Posted by Wilhelm2 View Post
    and hero swap is bad for evony? player A sends a hero to player B, player B buys a medalbox to be able to persuade it. Player B gets a hero,evony gets money
    i meant via the glitches that make the swap free.

  2. #322
    Join Date
    Sep 2009
    Location
    NORWAY
    Posts
    28

    Default

    well they fixed that, or at least they said so on the last pacth they did

  3. #323

    Default

    Quote Originally Posted by SupB View Post
    i meant via the glitches that make the swap free.
    alot of players are unaware that there is another way to transfer hero for free.
    I have seen non prinz player wielding top 100 hero that belong to another player. I won't say anymore.

    When I mean wielding i mean used it not just defense.


    In WAR, one must decide their faith, or others will decide yours.

    Think you can read it without laughing? Go ahead and try it http://bbs.evony.com/showthread.php?...19#post1810519

  4. #324

    Default

    Quote Originally Posted by SupB View Post
    are there other pressing things that need more attention before than this? YES!!! However, evony has shown a track record of "fixing" things we never have a problem w/.
    Then why support the "status quo" of repeating that same process? Your endorsing of the change is equivalent to a "blank cheque" approval for the company to continue to do the same thing, instead of suggesting that the company take more time and evaluate things.

    The thing I'm noticing is the things they're fixing most of the time are attributed to "spirit of the game". Which means its not what they intended for the game to be like, so they're trying to fix it (2+ years later).
    Rushed development, including rushed patches, lead to exactly this situation. From a development standpoint, I have no idea of how to classify their development cycle in industry terminology.

    They are clearly not "extreme programming", "Agile", or "Rapid Application Development". All of those have at their foundation a series of smaller changes in a more rapid pace to respond to changing customer requirements. Customers are not consulted here very much, thus that's out the window. Not only that, but changes may happen once every 3 months, or once a year, which is too wide of a timeframe to be considered Agile.

    They are also not following waterfall models, as again, customers are seldom consulted. Although waterfall development is slower, thus from that standpoint it's closer, the lack of customer consultation makes it not fit the classification either. Another cornerstone of waterfall development is that there is the Big Design Up Front. Since the phrase "not what we intended" is so often stated, that means that the design process was not thought through enough to make sure that the design would meet the requirements, aka "what was intended".

    I'm not arguing that this needed to be fixed over the many many many other issues w/ the game, but we gotta take things as they do it.
    On the contrary, "we" do not "have to". You may choose to, but others may choose not to.

    I apologize for looking like i breezed through what you said, but at this point i've repeated myself a lot. If you can't find my list I'll go look for it for you. It was quoted a few times, so it shouldnt be difficult to find.
    So have people who are making logical arguments against proceeding with this plan.

    I do know where your other post is, and I will still go look at it, but the general tone of what you're saying is simply "we have to accept it". While that may turn out to be ultimately true, it does not speak to why the change is a good thing. If you are unable to argue that a change is a good thing, generally speaking, the change should not take place.
    Last edited by neko_lord; 11-27-2011 at 10:55 PM.

  5. #325

    Default Differents Cooldowns Depends on Discharge

    I agree with some sort of cooldown being implemented, but frankly 72hrs is too much. I had to help an alliance member with a city, and left my alliance to help and now am 30 hrs from rejoining. I understand what is trying to be done, and also understand the points people are trying to make about abuse of city swap, hero transfer, and pres drop. I'm sure this isn't what Evony had in mind when this game idea was first though of and implemented.

    However I do believe that this is just part of the game now. That would be nice if all of the above options were implemented into the game with a discharge system kind of like the military. The three options being Honorable, General, and Dishonorable. These options would be dependant on how you were in the alliance that is booting you.

    1. Being booted from an alliance with a Dishonorable would cause a 72hr cooldown. Reasons for being booted this way would be along the lines of spying, bad mouthing, sabotage, and inappropriate behavior. Others reasons can be anything that would have affected the alliance in a negative way.
    2. Being booted form an alliance with a General would cause a 24 hr cooldown. Reasons for being booted this way would involve inactivity, non-responsive although activity is shown, and such. Other reasons for being booted don't have to be bad they can just mean that this person never really did anything for the alliance thus received a boot because they never defended their lack of group participation.
    3. Being booted from an alliance with a Honorable would cause a limit of 2 alliance within 24 hrs. This means you are only able to be booted and join 2 alliances within the 24 hr period. Reasons for being booted from an alliance this way would be helping lower players, city capping, moving to friendlies for diplomat talks, and player just need to move on but was in good terms.


    The discharges above could give the player who was booted a buff stating Honorable, General, Dishonorable, and the cooldown time remaining. The discharge type would be chosen when the VH or Host went to boot the player. Although there still will be some players who abuse this type of system. I believe this would make alot of players happy because not only is it making everything fair it would also mark the players who have done things in a more malice manner. Just a though on a different way to go about this cooldown as there needs to be something done either way.

    Thanks

  6. 11-27-2011, 11:03 PM

    Reason
    Off topic

  7. #326

    Default

    Quote Originally Posted by Wilhelm2 View Post
    well they fixed that, or at least they said so on the last pacth they did

    yeah but as they're fixed people find new ones, so this cool down thing puts a wrench in that. all the "glitches" that get abused seem to involving leaving and re-joining alliances, so i think a big part of this cool down is to thwart that.

  8. #327

    Default

    ok I have to say that I disagree with any cooldown time for rejoining the alliance. The only thing it will do is make more alternate accounts to flood the map. Not to mention...If I wanted to drop a city, instead of npc'ing it I usually would give it to an ally, now your are penalizing that. One of us would have to leave the alliance and stay out there for 3 days unable to come back because of a cooldown that you all felt needed to be in place. Cap the number of times a person can leave and rejoin or jump alliances in 3 days....that makes more sense than leaving ppl out in the cold for that long.

  9. #328

    Default

    Quote Originally Posted by deadlysage View Post
    alot of players are unaware that there is another way to transfer hero for free.
    I have seen non prinz player wielding top 100 hero that belong to another player. I won't say anymore.

    When I mean wielding i mean used it not just defense.
    the ones that do know is why this rule has been put in..at least in part.

  10. #329

    Default

    Quote Originally Posted by neko_lord View Post
    Then why support the "status quo" of repeating that same process? Your endorsing of the change is equivalent to a "blank cheque" approval for the company to continue to do the same thing, instead of suggesting that the company take more time and evaluate things.



    Rushed development, including rushed patches, lead to exactly this situation. From a development standpoint, I have no idea of how to classify their development cycle in industry terminology.

    They are clearly not "extreme programming", "Agile", or "Rapid Application Development". All of those have at their foundation a series of smaller changes in a more rapid pace to respond to changing customer requirements. Customers are not consulted here very much, thus that's out the window. Not only that, but changes may happen once every 3 months, or once a year, which is too wide of a timeframe to be considered Agile.

    They are also not following waterfall models, as again, customers are seldom consulted. Although waterfall development is slower, thus from that standpoint it's closer, the lack of customer consultation makes it not fit the classification either. Another cornerstone of waterfall development is that there is the Big Design Up Front. Since the phrase "not what we intended" is so often stated, that means that the design process was not thought through enough to make sure that the design would meet the requirements, aka "what was intended".



    On the contrary, "we" do not "have to". You may choose to, but others may choose not to.



    So have people who are making logical arguments against proceeding with this plan.

    I do know where your other post is, and I will still go look at it, but the general tone of what you're saying is simply "we have to accept it". While that may turn out to be ultimately true, it does not speak to why the change is a good thing. If you are unable to argue that a change is a good thing, generally speaking, the change should not take place.
    let me first saying up front i apologize for such a short answer after your extremely well thought out answers.

    you're right. the thing is this is the FIRST time evony has included in us in fixing something they changed. the other actual glitches they fixed that people cried about were things that the programmers/developers never intended for us to do. which goes to what you're saying. yes they didnt plan ahead thinking of what ways we'd think up to circumvent things, but was it naaive? an oopsy? stupidity? it doesnt matter. they should have fixed these things years ago, but maybe they didnt have the means then? I don't know what their situation is w/ respect to programmers back then. bottom line is a lot of the time we're seeing them play catch up, but catching up w/ things in a weird order. they seem to be doing things that we dont complain about, but they deem necessary while letting other things go. fundamentally the game needs key changes to key parts of the game mechanics to make things whole. until/unless they focus on that we're just gonna have to keep putting out these little fires as they come up.

    i never said the change is a good thing, but that i understand some of why its being done. i do think some people abuse liberties we have in game play, so some type of cap/cooldown makes sense. however, its not something that needs to be looked at now. there's plenty of other things they can fix. i think that more than anything is whats irritating most people.

  11. #330

    Default

    Quote Originally Posted by SupB View Post
    no they changed it for a reason, and i listed them back in this thread.

    as far as your 10 city thing, limiting the amount of cities you can have has to do w/ the title and whatnot too, so they would have to adjust those quests. im one of those people that think you should never be done building, so making it possible to have a lvl30 rally. however, once you mess w/ one thing other dynamics change. thats what we're seeing here.
    This is an important point. We have to consider second and third order effects from changes we make. One thing can cause another, can cause another. We have to be mindful of those.
    Legendary Hero

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •