Community Event / Creation Buckyball Racing Club presents: The A* Challenge V2.0

CMDR: ElitePenguin
Ship Type: Diamondback Explorer
Ship Name: Diligence
Class: Unlimited
Time: 1:37:38

20240130162500_1.jpg
20240130180238_2.jpg
20240130180241_1.jpg
 
CMDR: ElitePenguin
Ship Type: Krait Phantom
Ship Name: Lonesome Phantom
Class: Unlimited
Time: 1:24:36

20240220130501_1.jpg
20240220142937_2.jpg
20240220142940_1.jpg

Spent a lot of time routing and practicing for this! Thankfully, I had no major goofs. Had just a few minor glitches & mistakes. I think God reminded me a couple times to enable the fuel scoop, because I am notorious for forgetting that! :p
 
Not to take anything away from @FlyingPenguin 's run, which is an amazing achievement in a Phantom. Either the few Ly less range doesn't make as much difference as I'd expect or they have a really well optimised route. Having said that...


CMDR: Ravenov
Ship Type: Anaconda
Ship Name: Wake Turbulence
Class: Unlimited
Time: 1:24:24


1ONaRgE.png


2MuajmO.png

8Chw5D6.png


tqs5tN6.png

SYOIHh1.png
 
CMDR: ElitePenguin
Ship Type: Krait Phantom
Ship Name: Lonesome Phantom
Class: Unlimited
Time: 1:24:06



Praise the Lord for a practically perfect run! I honestly did not figure this time would be possible in a Phantom. I wasn't even sure I was going to try it again, but decided to anyway. I think this will be my last competitive entry in the Phantom...I am not sure how I could improve the time with the exception of one slow system, which would require a sketchy route overhaul and the Odyssey GalMap auto-plot bug towards the end. When @Ravenov beats this time again, I will most likely swap over to the conda as well.

I am considering posting the full video at some point, but might give it a while before I reveal any secrets ;).
 
Just heading out to see the galaxy in a different angle - so I thought, why not trying to do it a bit faster than usual for me. Here is the result:

CMDR: Sir Boundness
Ship Type: Krait Phantom
Ship Name: OUTA BUBBLE HUBBLE (https://edsy.org/s/vW3Se7j)
Class: Unlimited
Time: 2:33:18

I am not shooting for any leaderboard, just wanted to do the challenge once and see how fast I can manage. At least, ~30mins faster than spansh asumed I would be ;)

Start 31st March 19_56_11.jpg

Arrival 31st March 22_33_29.jpg

 
Update Incoming, new look on the way.


I'll be putting out a new leaderboard later today or tomorrow.
The post will also have a summary commentary, but I'm not not sure whether I have time to make that as detailed as some of the past ones – or as good as recent events deserve.

I'm also tidying things up in order to to make admin and updates easier for me in the future. This will include a google form for submissions, similar to the forms that we now use for all regular Buckyball races.

I now have an Excel spreadsheet that can generate Buckyball Leaderboards automatically from Google Forms data that I used for the recent BRC Race Once Upon a Time in Leesti.
I'll be using that as the basis for new A* Challenge Leaderboards. It's been tested by comparing against the google sheets autoboard that was used for earlier rounds of the Triple-8 championship, and if it can handle all the runs from the A* Challenge, then I can also use it for any future standing challenge that I host.

I hope to have the new automatic leaderboards up and running in the next two weeks - possibly sooner - I've got something else to get going on a different forum in the next few days though which will take priority. I'll be rearranging the first two posts of this thread to incorporate the new leaderboards and the updated rules from the next post. If I can't do that neatly enough, then I will start an A* Challenge V3.0 thread instead.

The main leaderboards will no longer be hidden inside spoiler tags in the OP, so everyone's runs will be on plain display, not just the record holders. The order of the three main boards will also change from "Classic - Neutron - Unlimited" to "Unlimited-Classic-Neutron", to reflect the fact that this challenge has been primarily about unlimited class now for a very long time.

Until the opening posts are tidied up, the new rules post below will be prominently hyperlinked from post#1​
 
Early Access Ships


The recent introduction of the Mandalay is the first of new ships that is likely to have a significant and lasting effect on the A* Challenge, so it's about time I addressed these "paid early access" ships, which may well be an ongoing thing.

Runs started during the paid early access period for a any new ship will be acknowledged, but only added to official boards one week after early access ends. The date of these runs will be adjusted so that the start date was one week after the day the paid early access ended.

E.g. if you make a run during a paid early access of a ship that begins at 00:30:00 08-DEC-3310 and the paid early access ends on 20-FEB-3311, then your start time will be adjusted to 00:30:00 27-FEB-3311. Your date will also be adjusted to maintain the correct run duration.

Any rebalancing of that ship between the date of your run and end of the paid early access period for that ship will invalidate your run, regardless of whether the rebalance makes the ship better or worse for the A* Challenge.

Once the paid early access period has ended, any future rebalancing of the ship will not affect the validity of past runs, but runs made prior to the rebalancing may have a note added to the leaderboard in the same way as very old runs made with the DBX, Orca or Type-7.

If you wish to be the first to set a record with a new ship, then please delay your run until the paid early access period ends. Any run made after the date & time that early access ended will be valid immediately. So any runs made during week 1 of a ship's full-release will appear to pre-date runs made during early access.
Note: These same rules will be used for any future ships or modules that have a limited early access period prior to being able to be acquired via gameplay in the main game, regardless of how the early access is acquired, e.g. cash, ARX, partner program, CG, etc.

Ships and modules that have a permanent limited access, will be handled on a case by case basis, e.g. ships or modules that are permanently paid DLC will be allowed (e.g. Odyssey only ships), limited edition CG prize ships or modules will not be allowed on the main boards if they perform better than items permanently available via gameplay (e.g. the Class 6A Pre-engineered FSD goes into Limited Edition Class, the Cobra Mk.IV does not).




Limited edition class.


This class was previously named "V1 Conda Class"

This class acts as a "quarantine zone" for runs made using ships or modules with permanently limited availability, that outperform assets permanently available to new players. In the event that a future ship or module surpasses its performance, runs made with that ship or module will be moved to the main leaderboards, but with their start time adjusted as per the rules for paid early access.

This currently includes the following ships and modules:
  • Class 6A Pre-engineered Frame Shift Drive.
  • No Limited Edition modules or ships currently exist in the game. 🎉
Example 1 - The Class 6A pre-engineered FSD currently outperforms all class 6A FSD drives currently available and can only be used by Cmdrs who participated in a selection of past community goals. For any current or future ship with a class 6 FSD slot, this is the optimal choice and it is not available to new players. This is no longer true, as V1 SCO drives of classes 2 - 7 are available to all commanders (in the live universe).

Example 2: The Cobra Mk.IV is only available to specific Cmdrs, but is inferior to other ships and so is valid on the main boards.

Example 3: The Class 3A pre-engineered FSD is also only available to Cmdrs who participated in specific CGs. It is inferior to the Class 3A (SCO) FSD and so is valid on the main boards.




Required Evidence


The following evidence is required for all runs. This can be provided by either a screenshot album (e.g. on imgur.com) or by two short videos, one for departure and one for arrival (e.g. on YouTube.com). The Google submission form will include two evidence link boxes, one mandatory, one optional:​
  • Outfitting – All Outfitting Screens or Module Tabs prior to launch, or in the Sagittarius A* system – full FSD engineering details must be shown.​
  • Start Date – This can only be provided by either the Galmap, the System Map or the Station Services screen, when docked in the starting station. Runs submitted without evidence of a start date will be assumed to have taken at least 24 hours to complete. E.g. a 3 hour run without evidence of the start date, will be assumed to be a 27 hour run.
  • Start Time (optional) – This is the time displayed on the Launchpad prior to pressing "launch". This time must be later than the time shown on the start date evidence.
    If no launch pad screen is provided, then the time from Station Services used for start date may be used. System / Galaxy map times can also be used, but will incur a ONE HOUR penalty, as they do not prove you were docked.​
  • End Date – Galmap or System Map – must show that you are currently in the Sagittarius A* system.​
  • End Time (optional) – An in cockpit screenshot from the Sagittarius A* system taken no more than 60 seconds prior to the time shown in the end date evidence (or from the same video clip as the end date evidence). This can be the time at the instant that you drop-out of hyperspace into the Sagittarius A* system.
    If no in-cockpit time is provided, then the time shown in the GalMap / System Map evidence will be used instead. This will incur no penalty other than being a little later than a system entry screenshot.​
IMPORTANT: Evidence of Outfitting
  • Runs without evidence of outfitting will still be accepted, but as outfitting is used to determine the class of your entry, some assumptions will be made about your run.​
  • Classic Class runs must include evidence that no banned modules are fitted.
    Failure to do so will mean that it is assumed that your ship has the best available modules for that ship type and your run will be moved to unlimited class or limited edition class.​
  • Frame Shift Drive evidence must show the exact type of drive fitted and any engineering.​
    • Failure to provide these details will mean that it is assumed to be a "pre-engineered" FSD with SCO, except for Class 6 FSDs, which will be assumed to be limited edition pre-engineered modules.
  • Without evidence, it will be assumed that your ship is fitted with Guardian FSD boosters and any future optional / utility module that boosts jump distance.​



Standard Race Classes:


Classic Class:
  • Start station must be Galileo in the Sol system or Lomas Orbiter in the Wolf 359 system.​
  • All ship types are permitted.​
  • Engineering is banned.​
  • Tech Broker modules (e.g. guardian FSD booster) are banned.​
  • Frame Shift Drives with Supercruise Overcharge (SCO) are banned​
  • Synthesis is banned​
  • FSD Boosts via white dwarfs or neutron stars are banned​
  • Use of Fleet Carrier or Megaship Jumps are banned.​

Neutron Class:
  • FSD Boosts via white dwarfs or neutron stars is permitted, including pre-charging prior to the start.​
  • All other rules are exactly as per Classic Class above.​

Unlimited Class:
  • Start station must be Galileo in the Sol system or Lomas Orbiter in the Wolf 359 system.​
  • All ship types are permitted (but see rules for Early Access Ships above)​
  • Engineering is permitted.​
  • All modules are permitted, including Tech Broker modules (but see rules for Limited Edition Class above)​
  • Synthesis is permitted.​
  • FSD Boosts via white dwarfs or neutron stars are permitted, including pre-charging prior to the start.​
  • Use of Fleet Carrier or Megaship Jumps are banned.​

Special Race Classes:


Limited Edition Class:
  • Limited edition ships and modules that are superior to those available to new players via gameplay or DLC purchase are permitted (e.g. Class 6A Pre-engineered FSD)
  • All other rules are the same as unlimited class.​
  • Since the release of Pre-engineered (V1) SCO drives, obtainable from Human Tech Brokers, no limited edition class is necessary.​
  • The one listed run, Darplata94's "direct run" record in a V1 Conda, is now Unlimited Class and will be absorbed into the unlimited class table in the next update.​

Double or Nothing Class:
  • This is a "for fun" class originally intended to only run for a short time alongside the Colonia Speedrun Competition
  • Start from any Station within 300ly of Sol​
    • This was originally the Fullerene C60 system, but as various systems have been used to begin a Colonia speedrun, we're allowing more flexibility.​
  • Must Dock at Jaques Station in the Colonia system before continuing to Sagittarius A*​
  • A timeout is allowed at Jaques Station:​
    • 30 minutes per unit of any rare commodity hauled from the bubble and delivered to Jaques Station. The BRC recommend "Bucky Ball Beer Mats" from Rebuy Prospect in Fullerene C60.​
    • The bonus for Bucky Ball Beer Mats is doubled to 1 hour per unit.​
    • This timeout only applies to the Double or Nothing Leaderboard.​
  • As other rules are the same as classic / neutron / unlimited class, and entries will be marked up to show which of those they used.​
Note that if this run would be fast enough to appear on the unlimited board (e.g. if this is your first run in that ship type) then it will also be added their, with a note denoting a Double or Nothing run, but without the rare commodity timeout adjustment.

Fleet Carrier Class:
  • You must begin your run in a starship, docked in a station, as per the standard classes.​
  • Start station must be Galileo in the Sol system or Lomas Orbiter in the Wolf 359 system.​
  • Must dock with a fleet carrier you own in the start system.​
  • Must travel to the Sagittarius A* system using manual Fleet Carrier jumps only, in the same Fleet Carrier you docked with at the start.​
  • No automation of your fleet carrier navigation/comtrol using macros or third party tools is permitted.​
  • You must remain in the same system as your fleet carrier during the entire run.​
 
Last edited:


November 3310 Update (1 of 3)

Well, at least it isn't 3311 yet...

Okay, so I didn't keep the thread up-to-date so well, but I did keep in touch with the participants via the BRC Discord, and we have had some EPIC racing in the A* Challenge since the last update, as well as several A* Challenge milestones.
Things began relatively quietly at the end of January, as Cmdr ElitePenguin (@FlyingPenguin), fresh from setting the first sub-90 minute time in a non-Conda earlier in the month in his Krait Phantom, turned his attention to the Diamondback Explorer. Arriving at the core in an incredible 01h37m38s, ElitePenguin smashed the existing DBX record by more than 30 minutes in Diligence. It wasn't another sub-90 run, but is by far the fastest ever run in a small ship.

Next Cmdr ElitePenguin switch back to his Phantom Lonesome Phantom and an epic battle began, the likes of which hasn't been seen since Ravenov achieved dominance of the challenge in 3306.

On 20-Feb-3310 ElitePenguin arrived at Sadge in Lonesome Phantom 01h24m36s after departing from Galileo, taking two seconds off the existing A* speedrun record. This run achieved the seemingly impossible and marked the first occasion since 02-May-3301 that the record had not been held by an Anaconda.

Four days later Cmdr @Ravenov was back. Running in the Conda Wake Turbulence, Ravenov retook the record with a run of 01h24m24s on 24-Feb-3310. That record lasted only until the 26th, when ElitePenguin in Lonesome Phantom set yet another new record of 01h24m06s, which remains the record time in a non-Conda.

March 3310 belonged to Cmdr Ravenov; making two more runs in Wake Turbulence, Ravenov knocked 25 seconds from the record with times of 01h24m01s on the 1st and 01h23m41s on 13-Mar-3310.

That marked the 14th time that Cmdr Ravenov had set a new A* Speedrun record, a staggering achievement and combined with setting the non-conda record eight times, Cmdr Ravonev is a true legend of Buckyball racing. o7 Cmdr!

In April Cmdr ElitePenguin made, what is for now, the decisive move. Switching to an Anaconda of his own, ElitePenguin made two runs in Wanda (not to be confused with @Esvandiary's Rhonda), setting new records each time. A run of 01h22m16s on 22nd was followed up the next day another record run (but not his last one, see update 3 of 3 below) of 01h21m39s.

o7 Cmdr ElitePenguin and o7 Wanda the Conda!

While the battle raged between the two fastest pilots in the galaxy a BRC Championship regular @CMDR Sir Boundness quietly arrived at Sagittarius A* in his loudly named Krait Phantom OUTA BUBBLE HUBBLE in a very respectable time of 02h33m18s, Sir Boundness became the 26th Buckyball Racing Club member with access to the Three Hour Club lounge at Rebuy Prospect in Fullerene C60.

Sir Boundness modestly commented, "I am not shooting for any leaderboard, just wanted to do the challenge once and see how fast I can manage. At least, ~30mins faster than spansh asumed I would be," however, this run was a major milestone in the history of the A* Challenge and so deserves a post of it's own (see update 2 of 3 below).

The last uplimited run of this update was, unsuprisingly, made by Cmdr @crotalus. On 08-Aug-3310 Crotalus made a run of 03h08m56s in Liasis. This run the first A* Challenge run in the new Python Mk II, and only the second ever run powered by the latest generation of frame shift drives with supercruise overdrive technology, offering A* runners a slightly increased jump range at the expense of increased fuel consumption.

Three days later, and again to the surprise of no A* Challenge fans, Cmdr @Darplata94 took a Python Mk II of his own - this one unengineered and with the SCO drive replaced with a standard FSD - to the core in a slightly longer time of 13h52m25s to take yet another Classic Class record.

Congratulations to both Crotalus and Darplata94, the A* Challenge record tables would look a lot different without you.

With galaxy's first ever dedicated Buckyball racing ship the Mandalay only months away from entering full production at the Zorgon Peterson shipyards, the era of the Anaconda looks to be almost over. The oldest record in Buckyball, Alot's 07h56m41s Classic Run of 31-May-3301, looks set be shattered early in 3311 - Darplata certainly has his eyes on it and has offered Cmdr Alot the chance to go head-to-head when the Mandalay Racer enters full production.

If you fancy having a go yourself, in Classic or Unlimited, remember that runs made in preproduction Mandalay's will not be valid until one week after full production begins, and may be disqualified if Zorgon Peterson are force to make late changes to the production vehicles.

Unlimited_Board.png


For Classic Class I'll just include the records table for this post, as the full Classic Class table is huge - the full leaderboard is on page 1 of the thread.

Classic_Records.png


 
Last edited:


November 3310 Update (2 of 3)


The arrival of @CMDR Sir Boundness at Sagittarius A* on 31-Mar-3310 appeared routine enough, and a great time of 02h33m18s was more than good enough to gain entry to the Three Hour Club.

The run did however mark a major milestone for the A* Challenge, as Sir Boundness became the 200th Commander to enter the BRC A* Challenge and its predecessor the Buckyball Run A* in the 9 years since @ElectricZ began the event.

Here is a full list of all 200 Pilots Federation members who have competed in the event since the beginning, including their personal best time. This includes Cmdr ElitePenguin's (@FlyingPenguin) very best run from the post below (see update 3 of 3).

Best_Runs.png
 
Last edited:


November 3310 Update (3 of 3)


Cmdr ElitePenguin (@FlyingPenguin) already held a two minute advantage over any other Commander to make an A* Speedrun, but wasn't going to wait for Zorgon Peterson to pull their fingers out with their new Buckyball Racer before trying something new. ElitePenguin replaced Wanda's Traditional Frame Shift Drive with a brand new one, incorporating cutting edge Supercruise Overdrive technology and went again.

The new drive technology allowed ElitePenguins to set a fantastic new A* Speedrun Record of 01h15m05s on 18-May-3310 and in that configuration Wanda is currently the fastest ship in the galaxy (once it makes the jump to hyperspace).

As the Age of the Conda enters it's twilght, the SCO Era begins with Wanda sat defiantly at the top of the boards.

Unlimited_Board.png


Here is the history of the record, from @Zulu Romeo's historic first visit nearly ten years ago, to the present day. The non-conda record history is inside the spoiler tags, however with the full production release of the Zorgon Peterson Mandalay Racer only months away, the non-conda history will soon become of historical interest only, and will be retired to the "history of the A* Challenge" section.

Record_History.png


Non_Conda_Record_History.png
 
Last edited:
I've a few little corrections to make to the above posts, as @FlyingPenguin has let me know that his final run in Wanda was an SCO run, not V1. My mistake, mixing up the drives when updating everything.

That means, it is obviously a completely official unlimited class run, and also was earlier than @crotalus' SCO run in the Python Mk II.

Sorry about the mix up, I'll get the posts tweaked later today. 😊

EDIT - I think everything is correct now.
 
Last edited:
I've updated the leaderboards in the OP with the runs from the last update.
I think they're all up to date now, sorry for forgetting I hadn't done it - thanks for the reminder @FlyingPenguin

The textual history in the OP is still badly out of date, but I believe the class history tables are finally all correct, and my spreadsheet now has a semi-automated alert if a class is missing or the latest record hasn't been added to those (really hard to update) tables.

I've also updated the latest rules post, because 🎉"hallelujah!!!"🎉 the new pre-engineered SCO drives are available to all Cmdrs via Human Tech Brokers in the "Live" universe. So currently "Limited Edition Class" no longer exists. I'll be merging Darplata94's V1 Conda "Direct" run into unlimited class in my next board update.

Looking at how I've laid out that rules post and how the OP is set out, it doesn't look like too much effort to fix the OP, so I'll try to get that done in the next week, while I'm on holiday from work. 🤞

Hopefully the current galaxy wide temporal storms that are disrupting hyperspace jumps throughout the galaxy will soon abate so we can get back to Buckyball and set some new records with those snazzy new V1-SCO drives.
 
Back
Top Bottom