The event was extremely confusing and chaotic. KNF not able to find their way out from Tohoku to Earthart. Then confused about getting out from Earthart only to land in Kepler of all places. Then confused more about a bunch of unexpected additional enemies. Then confused whether KNF IDed ships can proceed into Colorado.
Then in the end LN getting confused about the Lifter not responding to the commands anymore.
Had a hunch Hackers would crash it when I saw the list of Cyphers before the event.
I loved it!
The only bad parts were LN outnumbering us in the beginning, general lack of care for the objective on the KNFs part and Kepler being such a pain to fly in.
Coming in late, I thought the Hackers in Kepler were merely shadowing the fleet, like Auxo usually does. After jumping from Earhart and realizing the tail end of the group is being shred to pieces by people who weren't listed on the event page, I figured something was up.
Reading a lot of what's here, seems it was like this for the majority of people on both sides. I won't offer much criticism, but it seems like the team could do better with events like these.
I did get to kill a Komainu in Ontario with an LSC, though, so that was fun.
Posts: 6,544
Threads: 360
Joined: Aug 2007
Staff roles: Story Dev Economy Dev
Hi all
The Hackers were an intended surprise, yes. I asked for a wing to be assembled as a way of throwing a chaotic curveball at the event. From observing, the Hackers were generally outnumbered but were far more coordinated in Kepler. That said, I didn't expect the impact would be quite that decisive.
The exit JHs were also set to Kepler and Copernicus - I'm not sure why the names on the Earhart side didn't update, so I am sorry for the confusion that caused. I'm aware that this information being more accessible probably would have changed the calculus on where the fleets went.
As for the event ending, we had intended to run into engine problems and have the Lifter stall as soon as an intercept happened. But there wasn't one - my understanding is the majority of the participants were preoccupied with an unrelated fight in Galileo.
When the interceptors did arrive in Ontario, the Lifter halted (at Cochrane admittedly) to provide a chance for a last minute reversal. Unfortunately Barrier had a situation come up and had to leave immediately (which is where the F1 occurred).
We'll be reviewing the feedback and have already taken on lessons about how the event ran. We'll factor that in to future plans.
The Hackers were an intended surprise, yes. I asked for a wing to be assembled as a way of throwing a chaotic curveball at the event. From observing, the Hackers were generally outnumbered but were far more coordinated in Kepler. That said, I didn't expect the impact would be quite that decisive.
The exit JHs were also set to Kepler and Copernicus - I'm not sure why the names on the Earhart side didn't update, so I am sorry for the confusion that caused. I'm aware that this information being more accessible probably would have changed the calculus on where the fleets went.
As for the event ending, we had intended to run into engine problems and have the Lifter stall as soon as an intercept happened. But there wasn't one - my understanding is the majority of the participants were preoccupied with an unrelated fight in Galileo.
When the interceptors did arrive in Ontario, the Lifter halted (at Cochrane admittedly) to provide a chance for a last minute reversal. Unfortunately Barrier had a situation come up and had to leave immediately (which is where the F1 occurred).
We'll be reviewing the feedback and have already taken on lessons about how the event ran. We'll factor that in to future plans.
Thanks for the attempt, Jammi. Despite the vitriol I appreciate that the intent was there for a fun event.
[03.07.2024] LNS-Beast***: we can do this every day but you have to buy bigger stronger ships...and i'll help you
1. Please more console warnings/messages, most of people are indies who just follow the mass.
2. "Allstars" wasn`t outnumbered, they had like 10+ snubs which is deadly even if whole Liberty gathered (around 15-20) + Obviously people brought capital ships to fight in Earheart initially, and capital ships fleet just can`t really even contest against 10+ adequate lvl of playing snubs.
3. The route eventually also rather favoured the Hackers side. In my opinion, you could use Hackers side to be on a ready to deploy it against either Liberty/Kusari if one side would be winning significatly, then it actually would be a surprise and interesting and not just instalose to both sides, that would be better way to use them.
4. Don`t ever include outcomes such as "well argonaut can be damaged" while there is noone in charge on sides to make that decision. Moreover, I would suggest putting "commanders", there are more than enough of fine players for that, in charge of every side, to maintain equal oppurtunities. + I might wonder that kill squad was having a big advantage in knowing everything from the start.
In conclusion, great idea, but nearly disaster on practice, just a planned pew pew with bounties. My suggestion - make events in mind that all sides should be in equal oppurtunities or deploy "kill squads" only as a surprise to the current winning side. Otherwise it just kills any interest and might enbuild sterotype that all events are just rigged from the start.