Mr.X said:
Mad Dawg said:
Changelog:
Spawn points on Curaw now fixed so all defender troops spawn inside of keep.
[quote author=Curaw Event]
LES CodeX: Spawn is ****
Some random balion, think ron burgundy: same spawns as last time
Some random balion, think ron burgundy: gf absentmindedness
Seriously, those spawns were **** if we were supposed to defend, considering attackers were on the wall before the defenders
[/quote]
The "spawn points fixed" is what Ron was referring to. 1 out of 8 people would spawn outside the keep in the previous fight due to 1 entry point not being place. Was a map issue, not a module issue.
Considering the spawns were in the most defensable position on the map, not sure what the problem is. Whether you are trying to defend the front walls or the keep it's all defendable and the goal is the same. With the event one of the main goals was to shift everyone's thought process away from timers, flags, and whether we are keeping them out of the castle or not. I trying to convey that it's all about kills and a defender can be a defender.
The defenders were pushed back into the keep systematically. They were fighting on the walls and in the streets just as they did last time. About midway through we setup and accomplished taking the left side (to your spawn) inner wall portcullis forcing you back into the keep. It was a timed assualt that worked. You were then placed into an extremely defensible position that favored you, not us. If you wished to get out of the keep, you could have mounted an assualt and killed all of us thereby taking back the inner wall's gates and kept pushing from there.
Really the spawns being where they were kept you alive longer as when we pushed in and killed a number of you the "reinforcement troops" spawned right in the middle of us. It's not a perfect system but I find it far more enjoyable than the standard "flag" system forcing defenders to make costly moves trying to hold a flag in the open.
It's possible a 1 minute delay in the assualt would allow you to push further forward and defend the outer parameter wall, which we have done before with success, but it require people understanding this which seems to be an issue in information transfer.
Agree that the tk exploit is a big issue that will look to be fixed. Unfortunate it has to be and was used to the extent it was.
All in all this is a learning experience for us as much as it is for you. From the number of people that continually were asking for information last night, it seems more study needs to be done on the provided information.
Good times, of course.