[DW2] Basecamp Events

Archived thread. For info on the DW2 Organized Mass Jumps, hop to our new central info thread:

DW2 Unofficial Mass Jumps
DISTANT WORLDS 2 - ORGANIZED MASS JUMPS

Next upcoming jump:

JUMP 08:
Goliath's Leap - Departure from Waypoint 8, Sunday, March 24th, 20:00 UTC, Fleetcomm Private Group, PC


Swoals IL-Y e0--->Swoals RW-W D1-2

Next Sunday, we will attempt our most challenging jump yet, and also probably the first large scale neutron mass jump in Elite: Dangerous.

UPDATE: Instance 1 is now full with 60 Commanders signed up. It is still technically possible to sign up there, but you will be put on a waiting list. We recommend signing up for Instance 2 at this time.

REGISTRATION IS REQUIRED FOR THIS EVENT. Sign up at the following SIGN-UP SHEET




    • We will wing people into two instances for this event. The first instance will be coordinated by ingame text chat, while the second instance will be coordinated on the Fleetcomm Discord voice channel dw2-events-voice. You can choose between the two instances during registration NOTE: Instance 2 will also have ingame text, and there is no need to talk on Discord if you just want to listen in.
    • Please check this Forum post for any important updates after you have signed up, especially on Sunday. We will also post regular updates on the #dw2-events and #dw2-massjumps channels to keep you informed.
    • Further information can be found below.

Mass jump from Sagittarius A* Source: CMDR Zer0axis (
Source: https://www.youtube.com/watch?v=VraVXyjXAiY

)

This post will be regularly updated with information and details about upcoming mass jumps from the waypoint systems, organized by CMDR Rebecca Lansing.

JUMP 08 - Goliath's Leap
Swoals IL-Y e0--->Swoals RW-W D1-2, Mar 24th, 20:00 UTC

GENERAL CONCEPT & TIMELINE (all times in UTC / INGAME TIME) - DETAILED INSTRUCTIONS ARE BELOW

  • Starting now until Sunday, 18:00 UTC: Registration for the mass jump at the SIGN-UP SHEET
  • 17:00: Signed up Commanders start gathering by themselves (no organized wing in) at the Hades Edge basecamp on Swoals IL-Y e0 B 1 ("Goliath's Rest" / WP8).
  • 18:00: Signed up Commanders launch together from Basecamp, supercruise to the Swoals IL-Y e0 main neutron star, supercharge their FSDs and wait in supercruise to be winged into the jump instances.
  • ~18:15: Wing coordinators start setting up the jump instances.
  • 18:30-19:55: Jump instance is set up, CMDRs who want to jump with us should standby in system & in supercruise to be winged in. Wing coordinators will start winging in CMDRs.
  • 19:55: Fleet mass honk, followed by final checklists.
  • 20:00 Mass jump to the Swoals RW-W D1-2 star system.
WING COORDINATORS FOR JUMP 08 - Please make sure to check for the final list of your wing coordinators before the jump!

INSTANCE 1 (Coordinated by ingame text chat):


CMDRs
  • Rebecca Lansing
  • Luna Valenwood
  • Bra2S
  • The Sonderval
  • Bolasie
INSTANCE 2 (Coordinated by Discord voice on the Fleetcomm Discord dw2-events-voice-channel):

CMDRs
  • Dr.Nagi
  • Diana Night
  • Mosta
  • Derage
DETAILED INSTRUCTIONS FOR THE MASS JUMP
  • Make sure you're on the PC platform and on the Fleetcomm private group, and you're familiar with wing procedures and dropping into wing beacons
  • Make sure you will be able to actually reach the Swoals IL-Y e0 star system (WP8: Goliath's Rest). Please consult the current route map on how to get there.
  • Register for the mass jump event at the following SIGN-UP SHEET
  • Check your entry on the ROSTER to see which roster number your entry is at. Both instances have a capactity of roughly 60 ships. If your roster number is above 60, you will be put on a waiting list.
  • Our wing coordinators will send you a friend request, make sure to accept them.
  • Familiarize yourself with the concept of neutron supercharging, if you have not done so before. We have prepared an instruction video for that, which also goes over the concept for this event. This other video also explains the intricacies of entering the jet cones of neutron stars very well. If you do not want to use the neutron supercharge, you can use an FSD injection to boost your jump range instead, if you have enough "jumponium" materials to do so.
  • Start gathering at the Hades Edge Basecamp on Swoals IL-Y e0 B 1 from 17:00. The wing coordinators will also be waiting there, so come join us as we go over final preparations. There will be no wing-in at that point yet, everyone can just land at the Basecamp by themself. This will also be a good opportunity to go over any questions you might still have.
  • At 18:00, we will all launch together from Basecamp, enter supercruise, and head over to the Swoals IL-Y e0 main neutron star. You should then supercharge your FSD at its jet cone. There's plenty of time to do so, so don't rush it and be careful! After your FSD is supercharged (or if you are simply using jumponium instead), get some distance to the neutron star and wait to be winged in to the jump instances.
  • At this point, please make sure that you really have the required range to reach our target system Swoals RW-W D1-2 (78.3LY) by either having supercharged from the neutron star or having boosted your FSD with a jumponium injection.
  • The wing-in to the jump points will start from about 18:30 and will continue to about 19:55. You will receive a wing invitation from one of our coordinators. Make sure you accept any friend requests from them, so they can add you to their wings.
  • Supercruise to the wing beacon of your coordinator and drop into our instance. Leave the wing after dropping to make room for the next CMDR. If you have any instancing problems dropping in, try messaging one of the other wing coordinators. Before you drop in, put 4 pips to SYS for maximum shield strength and keep it set up like that in case of any collisions. Be aware that other ships dropping in might me right on top of you.
  • Form up around the other ships in the instance and lock onto the Swoals RW-W D1-2 star system (78.3 LY away).
  • Check your fuel levels and consumption at this point, and make sure they don't drop below the level needed to make the jump. If you have a small fuel tank, you might want to shut down your thrusters or other systems to conserve fuel. We will have a number of refueling ships with us, so if you need gas, just ask.
  • At 19:55: After the fleet mass honk, standby for final checklists and announcements.
  • At 19:58: Charge your FSD and keep your throttle at zero.
  • At 20:00: Throttle up and engage. IMPORTANT: After you enter the jump, immediately throttle down again, because the jump target will be another neutron star!
 
Last edited:
Colonia Nebula Canyon Race 2 (DW2 Edition)


Event :


Colonial Canyon Racing 2 (DW2 Edition)


Organized and hosted by former CCN Events Team Leader : CMDR Mosta


The race will be held in the Fleetcomm PG


Communication will be held on the official FleetCommHQ Discord server


Videos from previous shenanigans (Credit: Maximillian Reach, Erimus Kamzel and Pi Equals 3)


[video=youtube;ASBk3U9hNOQ]https://www.youtube.com/watch?v=ASBk3U9hNOQ&t=[/video]


[video=youtube;SvqkramIxgU]https://www.youtube.com/watch?v=SvqkramIxgU&t=[/video]


[video=youtube;Z-Ut8KTGR_k]https://www.youtube.com/watch?v=Z-Ut8KTGR_k[/video]





Location :


Jaques System, Galmap ref: Colonia, Planet 7 A A


Gather at 43.6°/ -85.3° (near geo-signal 8)





Date and Time :


February the 16th 2019, at 19:00 Gametime





Rules :


Players may aquire a stock Viper Mk3 (EDIT: Availible at Colonia Hub on Colonia 2 A, not Jaques Station). To keep it fair and simple, customized outfitting, engineering, guardian tech, will not be allowed for the main race

There will be 3 runs



  • Each run will earn you points based on your finishing position.
  • 1st place will earn you 3 points.
  • 2nd place will earn you 2 points.
  • 3rd place will earn you 1 point.
  • The points will add up to a final high score to decide the winner.
  • If there is a draw after the third run, the competing players for the 1st place will race together in a final lap to decide the winner.


Further rules:



  • No ramming
  • No weapons fire
  • Try to stay below 500 meters
  • Stick to the course
  • Take no short cuts (observers will be on hand to check!)


The winner will recieve a free paintjob of their choice



For those that wish to join, after the main race there will be a couple of no-prize runs, with no ship, module, guardian tech, or engineering limitations. Prepare and bring whatever ship and loadout you want and prepare for fun and explotions. (standard FleetComm rules still apply, so no weapons or destructive ramming)





Racers Route :



High res picture: http://i.imgur.com/FpI8PrU.jpg


Video walkthrough of the track (Credit: Maximillian Reach): https://www.youtube.com/watch?v=Dxzgfq_WlTw


I highly recomend doing a couple of training runs before competing. I will be in the area before the event to wing people in







Sign up form :


https://goo.gl/forms/rSDYwwtfEC1jedVD3

Contact Mosta on the FleetCommHQ Discord server for further questions or inqueries. Make sure to send a friend request in advance of the event





 
Last edited:
WP5 Event: Grand Formation

Organizer: Corbin Moran

IMAGES AND VIDEO FROM PREVIOUS EVENT. THIS ONE WILL BE GRANDER!


Description:
  • We will try building the greatest formation for surface maneuvers ever attempted!
  • We will perform stunts never tried before.
  • We will end the event with a coordinated mass jump in formation while traveling at speed.

Event Location, Player Group, and Platform:
  • WP5 system BOEWNST KS-S c20-959, body A 2 A, Biological Site 2. (But just wait in super cruise to be winged in).
  • Event will take place in the FleetComm private group.
  • This event is for those on PC only (sorry).

TIMELINE (all times in UTC / INGAME TIME)
  • Saturday, 16th Feb, 12:00: Registration for the event closes.
  • Sunday, 17th Feb, 18:00: Wing-in begins. Wing coordinators will start getting people into the instance. Once the first 10-12 people is instanced they will be assigned their own instructor for some warm-up formation practice. Same with the next group of 10-12 people we get inside. Arrive early and you will get more time to practice.
  • 18:45: Wing-in concludes. Building the Grand Formation. All pilots in the instance assemble and we start building the grand formation.
  • 19:00: Maneuvers and stunts. We will try out some stuff never attempted before…
  • 19:50: Mass Jump Preparation. We start lining up for the formation mass jump.
  • 20:00: Mass Jump. We start the journey towards WP6. End of event.

Communication:
  • We will be using the FleetComm discord for voice comms (microphone required for instructors/flight leaders).
  • Look for the voice channel named “dw2-events-voice”
  • Look for the text channel named #dw2-events-text
  • During the warmup phase of the event, smaller groups and their instructors might use the DW2 Wing Chat discord channels.

Requirements:
  • No previous experience with formation flight is required, but situational awareness and a steady hand on the stick are important qualities for a formation pilot.
  • All ship types are welcome (we once had a T9 lead a formation at Beagle Point…).
SIGN-UP:
  • Sign-up prior to the event IS required.
  • Sign up using THIS DOCUMENT.
  • IMPORTANT UPDATE: Sign-up will close Saturday 16th at 12:00 UTC.

WING-IN COORDINATORS FOR THE GRAND FORMATION EVENT
CMDRs
  • Rebecca Lansing
  • Luna Valenwood
  • Dr.Nagi
  • Tenna
INSTRUCTIONS FOR THE WING-IN TO THE EVENT
  • Make sure you're on the PC platform and on the Fleetcomm private group, and you're familiar with wing procedures and dropping into wing beacons
  • Make sure you are registered for the event and have correctly entered the required information in THIS DOCUMENT
  • Make sure you're present in the WP5 system BOEWNST KS-S c20-959 from 18:00 (the earlier the better), preferably near body A 2 A, where you will be winged in by one of the coordinators. Make sure you accept friend requests from the coordinators, so they can add you to their wings.
  • Please note that we can't guarantee to get you into our instance. We will try to get in about 45 CMDRs, but we will conclude the winging in depending on server performance and system instability. To improve your chances of taking part, make sure to accept friend requests and wing invitations from the coordinators promptly and be at the WP5 system no later than 18:00.
  • Supercruise to the wing beacon of your coordinator and drop into our instance. Leave the wing after dropping to make room for the next CMDR. If you have any instancing problems dropping in, try messaging one of the other wing coordinators.
  • Keep 4 pips to SYS for maximum shield strength and throttle to zero when dropping in in case of any collisions. Clear the area where you dropped in and await further instructions from your formation flight leader, who will take over for the actual formation event.
  • Once you arrive: DO NOT turn on external ship lights. And DO NOT deploy your SRV. This has been known to decrease performance drastically in the instance.


IMPORTANT SAFETY NOTICE:
So far we have never had any accidents, but formation flying involves an element of increased risk - it is part of the fun and the thrill. By taking part in this event you accept the increased risk of losing your ship. Don't fly without a rebuy!

How NOT to arrive if you are late to the event :)


Looking forward to threading some loops with you :D

Corbin
 
Last edited:
Updated with some notes on the formations and maneuvers we will be trying: Notes on The Grand Formation

Also please note that we will be doing almost 2 hours of flying before the final mass jump. WE WONT BE ABLE TO WING IN PEOPLE FOR THE MASS JUMP ONLY!
 
Last edited:
IMPORTANT UPDATE: Sign-up for the Grand Formation will close Saturday 16th at 12:00 UTC.

We have already received a lot of interest in this (which is great!) but we are also approaching the limit of what is technically feasible to achieve with instancing.
We will need a bit of time after sign-up closes to plan the event according to the number of people signed up, as well as what types of ships they bring.
Sorry for any inconvenience.
 
DISTANT WORLDS 2 - UNOFFICIAL MASS JUMPS

Next upcoming jump: Sunday, February 24th, 20:00 UTC

JUMP 06:
Departure from Waypoint 6, DRYAU AUSMS KG-Y e3390,
Fleetcomm Private Group, PC


REGISTRATION IS REQUIRED FOR THIS EVENT. Sign up at the following SIGN-UP SHEET


Unofficial mass jump from WP4. Source: CMDR Zer0axis (https://www.youtube.com/watch?v=qSrDGuI5Jc8)

This post will be regularly updated with information and details about upcoming unofficial jumps from the waypoint systems, organized by CMDR Rebecca Lansing.

JUMP 06:
DRYAU AUSMS KG-Y e3390 (WP6)--->DRYAU AUSMS XX-U D2-1560, Feb 24th, 20:00 UTC

TIMELINE (all times in UTC / INGAME TIME)
  • Starting now until Sunday, 19:00 UTC: Registration for the mass jump at the SIGN-UP SHEET
  • 18:45: Wing coordinators start setting up the jump instance.
  • 19:00-19:55: Jump instance is set up, CMDRs who want to jump with us should standby in system & in supercruise to be winged in. Wing coordinators will start winging in CMDRs.
  • 19:55: Fleet mass honk, followed by final checklists.
  • 20:00 Mass jump to the DRYAU AUSMS XX-U D2-1560 star system.
WING COORDINATORS FOR THE WP6 JUMP
CMDRs
  • Rebecca Lansing
  • Luna Valenwood
  • Blockadefan [GPL]
  • Dr.Nagi
  • Diana Night
TAKING PART IN THE MASS JUMP
  • Make sure you're on the PC platform and on the Fleetcomm private group, and you're familiar with wing procedures and dropping into wing beacons
  • Register for the mass jump event at the following SIGN-UP SHEET
  • Our wing coordinators will send you a friend request, make sure to accept them.
  • Make sure you're present in the DRYAU AUSMS KG-Y e3390 star system (WP6) no later than 19:00, where you will be winged in by one of the coordinators. Make sure you accept any friend requests from the coordinators, so they can add you to their wings.
  • Supercruise to the wing beacon of your coordinator and drop into our instance. Leave the wing after dropping to make room for the next CMDR. If you have any instancing problems dropping in, try messaging one of the other wing coordinators.
  • Keep 4 pips to SYS for maximum shield strength in case of any collisions. Be aware that other ships dropping in might me right on top of you.
  • Form up around the other ships in the instance and lock onto the DRYAU AUSMS XX-U D2-1560 star system (closest one on the nav panel).
  • At 19:55: After the fleet mass honk, standby for final checklists and announcements.
  • At 19:58: Charge your FSD and keep your throttle at zero.
  • At 20:00: Throttle up and engage.
Got to say poor organisation of this mass jump, was waiting an hour in supercruise only to miss it. Judging from expedition voice the only people even getting winged into it were people not on the sign up list.

None of the organisers using FC events channels either, so no clue what was happening over the noise of the rest of the expedition chat.
 
Got to say poor organisation of this mass jump, was waiting an hour in supercruise only to miss it. Judging from expedition voice the only people even getting winged into it were people not on the sign up list.

None of the organisers using FC events channels either, so no clue what was happening over the noise of the rest of the expedition chat.
You were apparently invited several times into a wing for the second instance, and didn't accept these invites. Sorry, but we can't wait for everyone.

We had 100 people on the sign-up list, and we got about 80 to jump across two instances, with five people doing the coordination, including one who only jumped in during the last two hours. If you think this was badly organized, feel free to try it yourself.
 
Last edited:
You were apparently invited several times into a wing for the second instance, and didn't accept these invites. Sorry, but we can't wait for everyone.

We had 100 people on the sign-up list, and we got about 80 to jump across two instances, with five people doing the coordination, including one who only jumped in during the last two hours. If you think this was badly organized, feel free to try it yourself.
I received no invites, last wing invite I received in my log was on 21/02/2019 at 17:32:33 (days before the mass jump) and no response from two of the organizers as to what was happening until seconds before the jump by which time I was already reaching for the log out menu.

Absolutely no coordination via Fleetcomm discord event channels regarding winging in or even the status of the jump... none... zilch. The only wings I could see being organised for were for people not on the damn list, who showed up at the 11th hour bewildered to whether there was even a mass jump.

I understand there was obviously a lot of demand given the size of the expedition and I don't question the difficulty, however I've taken part in dozens of expeditions with literally hundreds of mass jumps (some more prepared than others) and not one despite following the correct procedure involved sitting in supercruise for an hour without any sort of clue as to what was happening. I wouldn't of minded waiting longer than an hour or joining a second group if that was at least communicated, but it seems to me any pre organised lists were chucked out of the window in favour of just winging in those screaming in system chat.

On top of that there was a complete void of communication, why wasn't Discord leveraged more effectively? I mean if you're organising a mass jump with up to a 100 signups isn't it a no brainer not to rely on the ingame chats?
 
I received no invites, last wing invite I received in my log was on 21/02/2019 at 17:32:33 (days before the mass jump) and no response from two of the organizers as to what was happening until seconds before the jump by which time I was already reaching for the log out menu.

Absolutely no coordination via Fleetcomm discord event channels regarding winging in or even the status of the jump... none... zilch. The only wings I could see being organised for were for people not on the damn list, who showed up at the 11th hour bewildered to whether there was even a mass jump.

I understand there was obviously a lot of demand given the size of the expedition and I don't question the difficulty, however I've taken part in dozens of expeditions with literally hundreds of mass jumps (some more prepared than others) and not one despite following the correct procedure involved sitting in supercruise for an hour without any sort of clue as to what was happening. I wouldn't of minded waiting longer than an hour or joining a second group if that was at least communicated, but it seems to me any pre organised lists were chucked out of the window in favour of just winging in those screaming in system chat.

On top of that there was a complete void of communication, why wasn't Discord leveraged more effectively? I mean if you're organising a mass jump with up to a 100 signups isn't it a no brainer not to rely on the ingame chats?
You are completely underestimating the workload of handling more than 100 signed-in CMDRs from our registration, to friends requests, to wing invites, to then finally getting them into our instances. There is simply no time to simultaneously monitor ingame DMs, Discord DMs, and several possible regular Fleetcomm Discord channels if you are busy winging in people and the whole chat and friends system starts lagging from the instance load.

You were signed up with the roster number 75:


The normal way we would have done this is to simply cut off registration after 60 signed-in commanders, because this is the maximum number an instance can conceivably hold without severe problems. We wanted to try setting up another instance to also give the later sign-ins a chance to jump with us, and we managed to get at least a few of those into our second instance.

I'm sorry if this somehow seems unacceptable to you, but it is not our job to provide mass jumps to you. We do this in our own free time playing an online video game, without even being part of the actual DW2 organizing team. We can try to provide an organization that allows people to take part in our events, within reason, but we can't guarantee participation in any form.

Demanding explanations from us when we regrettably didn't manage to wing you in yesterday won't do you any favors here. Yesterday, we had some people actually spewing profanities at us in chat when they didn't get a wing invite because all wing slots were full at that time.

If you think you could provide more effective organization under these circumstances, you are welcome to help out with coordination at our next event.
 
Last edited:
I received no invites, last wing invite I received in my log was on 21/02/2019 at 17:32:33 (days before the mass jump) and no response from two of the organizers as to what was happening until seconds before the jump by which time I was already reaching for the log out menu.

Absolutely no coordination via Fleetcomm discord event channels regarding winging in or even the status of the jump... none... zilch. The only wings I could see being organised for were for people not on the damn list, who showed up at the 11th hour bewildered to whether there was even a mass jump.

I understand there was obviously a lot of demand given the size of the expedition and I don't question the difficulty, however I've taken part in dozens of expeditions with literally hundreds of mass jumps (some more prepared than others) and not one despite following the correct procedure involved sitting in supercruise for an hour without any sort of clue as to what was happening. I wouldn't of minded waiting longer than an hour or joining a second group if that was at least communicated, but it seems to me any pre organised lists were chucked out of the window in favour of just winging in those screaming in system chat.

On top of that there was a complete void of communication, why wasn't Discord leveraged more effectively? I mean if you're organising a mass jump with up to a 100 signups isn't it a no brainer not to rely on the ingame chats?
Okay, let me get a few things clear here (I'm part of the organising team).
We had internal communication in a private discord groupchat, se we would have clear comms to coordinate.
We have put all signups on a google with roster numbers and assigned them to the wing-in people, who sent friend requests to everyone on their list. Since we got a lot more signups than we anticipated, we crated a second instance who was set to jump 10 minutes later to prevent server crashes.
This meant we had to divert our resources for the wing ins and there was only 2 peple for instance 2, who were a bit overwhelmed. Although we tried to get everybody in.
At some points we had full wings and simply could not invite more people, as we had to wait for the winged ones to arrive. I also received several wing requests while I was already winging other people.
So what happened is you got a time where the wing was full and had to wait, but then you didn't show up on the friends list anymore. There is only that much we can do.
Some people apperantly got very salty when they didn't receive wings, DON'T EXPECT TO GET INVITES QUICKER OR AT ALL WHEN YOU START SWEARING AT US. This goes for everyone, not particularly adressing you here Spaghetti.
And for lack of open communication on FC discord: It was already difficult to keep track of everythign that happened ingae, on the sheet and internally. If we had also started talkign to everybody on discord it would've gotten much more chaotic. Like this it worked pretty well. People show up on the friends list, they get invited, they arrive in the instance, the leave the wing, next one gets invited. Rinse and repeat. Jump target AND time had been anounced prior to the event. So if you don't get an invite right away, wait until you get one. We are keeping track on every singup so we'll get to you.
In the end I had one guy in my wing that jumped nearly 1000 ly and arrived just in time for the jump.
 
You are completely underestimating the workload of handling more than 100 signed-in CMDRs from our registration, to friends requests, to wing invites, to then finally getting them into our instances. There is simply no time to simultaneously monitor ingame DMs, Discord DMs, and several possible regular Fleetcomm Discord channels if you are busy winging in people and the whole chat and friends system starts lagging from the instance load.

You were signed up with the roster number 75:


The normal way we would have done this is to simply cut off registration after 60 signed-in commanders, because this is the maximum number an instance can conceivably hold without severe problems. We wanted to try setting up another instance to also give the later sign-ins a chance to jump with us, and we managed to get at least a few of those into our second instance.

I'm sorry if this somehow seems unacceptable to you, but it is not our job to provide mass jumps to you. We do this in our own free time playing an online video game, without even being part of the actual DW2 organizing team. We can try to provide an organization that allows people to take part in our events, within reason, but we can't guarantee participation in any form.

Demanding explanations from us when we regrettably didn't manage to wing you in yesterday won't do you any favors here. Yesterday, we had some people actually spewing profanities at us in chat when they didn't get a wing invite because all wing slots were full at that time.

If you think you could provide more effective organization under these circumstances, you are welcome to help out with coordination at our next event.
Sorry but I'm not buying the whole "too busy to use Discord" line, using events-voice and events-text could of helped you to coordinate more effectively and even if you're personally too busy to respond to everything information could still be relayed easier. I've personally seen discord used to organize many mass jumps or events even on the scale of your one, there is absolutely no reason why you shouldn't be using it to do the same. I never said organising an event like this mass jump was easy but that's more the reason why there needs to be clear lines of communication between those taking part so confusion doesn't make it more difficult.

Look at it from my shoes, I spent a whole hour on a Sunday in supercruise waiting patiently for an invite that I'd never receive and receiving no response when I ask what is happening. I hope you can understand that I feel a little burnt by the experience and put off from joining similar FC events in the future. You might be right when you said it's not your job to provide mass jumps for me but it's not my job to waste my time for you either, if it was my job you'd owe me £7.83 national minimum wage for the time I spent staring at the comms panel for a wing notification needlessly.

My point is even a simple bit of communication whether it's letting people know (either individually or collectively via an announcement) what instance they are likely to be in or even letting them know that there's no more room would of sufficed. If I was aware of the winging in situation via an announcement or something I would of understood.

Also while I don't condone those spewing profanities if they were on the list I can understand their frustration. I know for a fact as mentioned in my previous post that there were people getting winged in that were not even signed up to the jump, which probably made it harder for those that were signed up trying to get in.

So what happened is you got a time where the wing was full and had to wait, but then you didn't show up on the friends list anymore. There is only that much we can do.
Some people apperantly got very salty when they didn't receive wings, DON'T EXPECT TO GET INVITES QUICKER OR AT ALL WHEN YOU START SWEARING AT US. This goes for everyone, not particularly adressing you here Spaghetti.
I logged out at 20:00 on the dot after I heard the mass jump had occurred, I wasn't aware of the second instance organising or later jumps. The information in the post at the top of this page is all I had to go by in that the jump would occur at 20:00.

If you can't forward that information how am I supposed to know if nobody was prepared to share that information? That is my complaint, I'm not psychic... despite my username I'm not all knowing.

As for the swears that is absolutely nothing to do with me, I sent three very reasonable "asks" to two people before eventually logging out. It's not hard for someone to reply "we're on it".
 
Last edited:
Sorry but I'm not buying the whole "too busy to use Discord" line, using events-voice and events-text could of helped you to coordinate more effectively and even if you're personally too busy to respond to everything information could still be relayed easier. I've personally seen discord used to organize many mass jumps or events even on the scale of your one, there is absolutely no reason why you shouldn't be using it to do the same. I never said organising an event like this mass jump was easy but that's more the reason why there needs to be clear lines of communication between those taking part so confusion doesn't make it more difficult.

Look at it from my shoes, I spent a whole hour on a Sunday in supercruise waiting patiently for an invite that I'd never receive and receiving no response when I ask what is happening. I hope you can understand that I feel a little burnt by the experience and put off from joining similar FC events in the future. You might be right when you said it's not your job to provide mass jumps for me but it's not my job to waste my time for you either, if it was my job you'd owe me £7.83 national minimum wage for the time I spent staring at the comms panel for a wing notification needlessly.

My point is even a simple bit of communication whether it's letting people know (either individually or collectively via an announcement) what instance they are likely to be in or even letting them know that there's no more room would of sufficed. If I was aware of the winging in situation via an announcement or something I would of understood.

Also while I don't condone those spewing profanities if they were on the list I can understand their frustration. I know for a fact as mentioned in my previous post that there were people getting winged in that were not even signed up to the jump, which probably made it harder for those that were signed up trying to get in.



I logged out at 20:00 on the dot after I heard the mass jump had occurred, I wasn't aware of the second instance organising or later jumps. The information in the post at the top of this page is all I had to go by in that the jump would occur at 20:00.

If you can't forward that information how am I supposed to know if nobody was prepared to share that information? That is my complaint, I'm not psychic... despite my username I'm not all knowing.

As for the swears that is absolutely nothing to do with me, I sent three very reasonable "asks" to two people before eventually logging out. It's not hard for someone to reply "we're on it".
I can only say what I've heard form the others, as you were not on my part of the list for wing-ins: You didn't show up on the friends list when they had space. As to why they didn't reply to you: No idea. There was a lot of chatter going on so perhaps they simply missed your mesages.
Again, organising and coordinating all this is a lot harder than it looks, so accidents regarding that can happen.
Regarding public announcements on the fleetcomm discord: Noone of us has the permission to do so (hence unofficial mass jumps), tho that might change in the future, we're discussing the topic.
 
Am I the only one that really dislikes discord? I never liked IRC and this seems to be just the same. I admit I never took the time to explore all the possibilities.
 
Could we please get a google sheet with dates and times of events? This event fishing through several posts is not a good way to present data.
 
Sagitarius Climb Race.

Sagitarius Climb Race.

A 19km straight-line, 5km total climb with several peaks on the way, on a 0.04G moon. The target is to reach a needle shaped peak in the SRV located at 13.4250, 80.1754.
Then if you want, jump to the bottom as far as you can.

Start when you want and take it as a challenge or launch together at the proposed time if you want a race.
There are no prizes, just the joy of adventure.

Where: Juenae BC-B d1-2996 AB 2 b a
Time: 2019-03-17 15:00 UTC
Start line: 14.596415 , 77.638672
Goal: 13.4268, 80.1715

I advise to use E.D.I.S.O.N. to guide yourself to the waypoints. You can import both the start and the finish with this file.

WARNING! There is probably no chance of a successfull ship recall on the track. Care for your vehicle!

Overview of the track:


Flyby:


A couple of sneak "peaks" here.

Geronimoooooooooo!!!!!!
 
Last edited:
Top Bottom