Mohxy
|
  |
| Joined: 20 Dec 2010 |
| Total Posts: 5958 |
|
|
| 05 Aug 2016 10:45 PM |
This is a short outline of why the FC-TCD war ended early with no victor. I felt as if FC deserved to know a bit more rather than just the thread that ended the war, especially since (I think we can all agree) that our time was wasted. This doesn't go into full detail, but it covers some of the major stuff.
FC and TCD both signed a war thread (https://forum.roblox.com/Forum/ShowPost.aspx?PostID=195056108), which was in fact made by TCD themselves, which stated that no game changing updates would be implemented without the consent of the opposing side.
The exact term (quote) can be found here:
"-No game-changing updates made without consent to either clan's fort (cuilan!)" ------------------- FCC was actually pretty excited about this opponent because they had a good track record and were pretty "honorable," along with initial negotiations going smoothly. This thread basically signified the completion of the "negotiations" and the only thing that was left was to decide a war start date, which was pushed back a bit for their leader to get back (We talked with TCD for longer than what the thread date was).
Anyways, their fort was enjoyable and they were nice so FC was fairly generous (Hint for other clans!). We asked for very little changes to their fort, and some of the changes that were listed were them wanting it (Such as decreasing server size). ------------------- The issue(s) that occurred was after everything was already set in stone. As seen in that thread, bases were completed and terms were agreed upon. However, TCD did not view these terms as binding until the war actually started.
What actually happened was that TCD continuously updated their fort without asking for the consent of FC, or even informing us for that matter.
The first batch of updates we essentially let slip a bit because it didn't drastically affect gameplay and it gave TCD a bit more advantages, thus having more of a challenge. However, these changes were bearable and did not ruin the enjoyment of raiding their fort. We later approached them after updates and just asked what was up, and their leader talked about how their developer just liked to update and that he couldn't control him, but that there would be no worries for the war. TCD later refused to revert any updates.
The next batch was where it got messy, which is where some of the blame could be laid upon FC itself. FC did not bother checking their fort as they updated (As we expected them to abide by the terms set forth and agreed upon), so when I got back today and checked their fort, I saw a different fort than what was agreed upon. Our main negotiator was offline at the time so I had to wait for him, which came to be about 11 AM EST.
FC brought this stuff to the attention of TCD a few hours before the war started (We should have checked the fort before this) and we ran into some issues. TCD did not want to revert their updates and changed very, very little about their base.
Now, FC did not actually want them to revert their entire base and all these updates. Like I said earlier, we let the first batch slide because they did not affect gameplay majorly and TCD seemed like a nice group.
Our main concerns before the war started included the rampant amount of health orbs (Positioned all over where TCD rushes to attack us), the windows at A, the bridge at B, the rocket launcher, and still no cover at C. All of this was not approved by FCC (Other than the cover at C, which is one of the very little original changes we wanted).
TCD ended up only removing a small portion of the health orbs that we requested and essentially kept everything else. The time was very close to when the war was supposed to start so we figured we would test the base because we didn't want to stall or perhaps even end the war right there.
After raiding there, we decided there their updates simply made the fort unenjoyable and too drastically altered the gameplay from what was previously agreed upon. Not only this, but FC also realized some other updates that we had no clue about.
These updates found out during raiding included the removal of extra time after capturing a point (Which essentially made it so that you had to flawless the base and reduced the server time significantly) and being able to capture B from the roof (Accessed easily by where TCD's spawns were) rather than being on the actual cap point. Additionally, we learned that the rocket launchers had a knockback that consistently knocked off Raiders from the spawn point into oblivion/death (Especially since floors were removed near the caps, which we did not approve).
We decided to re-enter negotiations with TCD and talk about these updates that we felt too drastically changed the base and made it unenjoyable. The list that I personally wanted included:
- Removal of windows at A, removal of rocket launchers, removal of bridge at B, removal of being able to cap B from the roof, removal of blue wall at C, re-addition of extra time after capping
Keep in mind, every single one of these changes that I personally wanted were all base updates that were >unapproved< and >after< we agreed upon the war terms/bases.
Only an extremely little amount of changes were done for our wishes, and actually, the only thing removed was the blue wall at C (Which was supposed to be for Raiders).
FC was not satisfied with this, and after further negotiations, neither side could come to a consensus and the war was ended. While we could have technically taken a victory due to a breach of war terms, we felt that that would be a more "cheater" move, especially since there was so little raiding done (2 servers for each side). Thus, it was decided to end the war with no victor and go our separate ways.
I didn't bother including any "proof" because this is a message to FC. This isn't meant to "expose" TCD or anything, its just explaining to FC members why the war occurred the way it did.
Sorry for the inconvenience and we will be looking forward to the future.
Summary: Unapproved base updates on the side of TCD and refusals to reverse some of these changes ended the war.
FOR THE WOLF! |
|
|
| Report Abuse |
|
|
stix7
|
  |
| Joined: 28 Jun 2012 |
| Total Posts: 9769 |
|
| |
|
|
| 05 Aug 2016 10:46 PM |
who cares
-CommanderExalted |
|
|
| Report Abuse |
|
|
mcclos
|
  |
| Joined: 22 Mar 2013 |
| Total Posts: 7344 |
|
|
| 05 Aug 2016 10:46 PM |
So void on either side
*flex* |
|
|
| Report Abuse |
|
|
Frigiden
|
  |
| Joined: 03 Aug 2016 |
| Total Posts: 3528 |
|
|
| 05 Aug 2016 10:46 PM |
hydra would easily melt fc
hail hydra |
|
|
| Report Abuse |
|
|
|
| 05 Aug 2016 10:46 PM |
a war not successful
not surprised
|
|
|
| Report Abuse |
|
|
|
| 05 Aug 2016 10:47 PM |
| why are you reposting my thread, it was locked for a reason. |
|
|
| Report Abuse |
|
|
Mohxy
|
  |
| Joined: 20 Dec 2010 |
| Total Posts: 5958 |
|
|
| 05 Aug 2016 10:49 PM |
What are you talking about?
I wrote this up |
|
|
| Report Abuse |
|
|
| |
|
| |
|
Mohxy
|
  |
| Joined: 20 Dec 2010 |
| Total Posts: 5958 |
|
|
| 05 Aug 2016 10:56 PM |
I care, that's why I wrote this up.
Typed it all by myself. I'm dedicated to the wolf. |
|
|
| Report Abuse |
|
|
Seviro
|
  |
| Joined: 08 Dec 2009 |
| Total Posts: 46758 |
|
|
| 05 Aug 2016 10:59 PM |
declares autowin over A-SOV doesn't declare autowin against TCD because it would be "cheating"
xD!
https://www.roblox.com/sev3-item?id=290109654 |
|
|
| Report Abuse |
|
|
| |
|
stix7
|
  |
| Joined: 28 Jun 2012 |
| Total Posts: 9769 |
|
|
| 05 Aug 2016 11:01 PM |
| Because asov are cowards while tcd is not |
|
|
| Report Abuse |
|
|
Seviro
|
  |
| Joined: 08 Dec 2009 |
| Total Posts: 46758 |
|
|
| 05 Aug 2016 11:02 PM |
so updating your base and refusing to make updates isn't being cowardly
noted
https://www.roblox.com/sev3-item?id=290109654 |
|
|
| Report Abuse |
|
|
|
| 05 Aug 2016 11:03 PM |
@Seviro
We had multiple wins on A-SOV and raided plenty of times.
Each side during this engagement only had 2 raids each, and it was a war where our opponent actually entered rather than refusing thinking the clan would go away. |
|
|
| Report Abuse |
|
|
Seviro
|
  |
| Joined: 08 Dec 2009 |
| Total Posts: 46758 |
|
|
| 05 Aug 2016 11:04 PM |
so you can declare an autowin on a clan if you get some raid wins but not if they back out of your war and update their base O_o
https://www.roblox.com/sev3-item?id=290109654 |
|
|
| Report Abuse |
|
|
stix7
|
  |
| Joined: 28 Jun 2012 |
| Total Posts: 9769 |
|
|
| 05 Aug 2016 11:05 PM |
No because they actually started to communicate with us right after this war started to get bad
Something that adead couldnt do |
|
|
| Report Abuse |
|
|
Seviro
|
  |
| Joined: 08 Dec 2009 |
| Total Posts: 46758 |
|
|
| 05 Aug 2016 11:05 PM |
there was never an A-SOV - FC war so I'm not sure what you're referring to
https://www.roblox.com/sev3-item?id=290109654 |
|
|
| Report Abuse |
|
|
| |
|
Obtention
|
  |
| Joined: 07 Feb 2013 |
| Total Posts: 15509 |
|
| |
|
Seviro
|
  |
| Joined: 08 Dec 2009 |
| Total Posts: 46758 |
|
|
| 05 Aug 2016 11:06 PM |
raiding a clan and getting a handful of raid victories isn't winning a war lol
https://www.roblox.com/sev3-item?id=290109654 |
|
|
| Report Abuse |
|
|
stix7
|
  |
| Joined: 28 Jun 2012 |
| Total Posts: 9769 |
|
| |
|
|
| 05 Aug 2016 11:07 PM |
They didn't back out of the war, their fort was updated and they thought it was okay. This was a clan that actually engaged in negotiations and didn't decline us, and they raided us.
We didn't declare an "autowin" on A-SOV, A-SOV surrendered after we crushed their morale after getting wins at Legal. A-SOV surrendered by updating the fort and flat out refusing to defend. |
|
|
| Report Abuse |
|
|
Seviro
|
  |
| Joined: 08 Dec 2009 |
| Total Posts: 46758 |
|
|
| 05 Aug 2016 11:07 PM |
but there was no counter-raid nor acknowledgement of your war therefore it doesn't matter
that's like saying you beat VAK because you won at Kaznan
https://www.roblox.com/sev3-item?id=290109654 |
|
|
| Report Abuse |
|
|