Sorry if this was mentioned before but couldn’t the crew confirmations be verified through looking at crew retrieval?
Absolutely they could. But where's the fun in that?
Only if you trust WRG to have retrieval and portal match with no bugs. Knowing the state of their code I wouldn't count on that.
As a reminder, the original reason these threads were created was because at one point TP said they made a portal update and then months later we realized the update was broken and the crew weren't in the portal. So now players look to verify each crew.
If we really wanted to be thorough we should have a separate 1-4* voyage confirmation check since it's possible a crew is added to portal and not voyages or vice versa.
I do actually trust WRG to have portal/voyages/retrieval all lined up. If only because driving it all off one database field is far and away the simplest option, coding it in any other way would be more complicated, require more work and frankly no software developer with even the tiniest bit of sense would do it any other way.
For the record, a tiny bit of sense is roughly how much I credit the WRG development team with.
Unfortunately there are times where different systems are incompatible or you decided to slowly migrate to a new DB and are left with legacy features using the old DB and new features using a new DB. Especially when you remember that portals are one of the oldest features in the game and need to support custom packs in addition to the general pack.
How WRG would design portal/voyage/retrieval today vs how they evolved over 6 years may be very different. I'm sure if they were all designed today they'd share the same DB flag. But I'm not convinced that a second column or duplicate list wasn't added over the years because it was easier/quicker when they were in a time crunch.
Sorry if this was mentioned before but couldn’t the crew confirmations be verified through looking at crew retrieval?
Absolutely they could. But where's the fun in that?
Only if you trust WRG to have retrieval and portal match with no bugs. Knowing the state of their code I wouldn't count on that.
As a reminder, the original reason these threads were created was because at one point TP said they made a portal update and then months later we realized the update was broken and the crew weren't in the portal. So now players look to verify each crew.
If we really wanted to be thorough we should have a separate 1-4* voyage confirmation check since it's possible a crew is added to portal and not voyages or vice versa.
I do actually trust WRG to have portal/voyages/retrieval all lined up. If only because driving it all off one database field is far and away the simplest option, coding it in any other way would be more complicated, require more work and frankly no software developer with even the tiniest bit of sense would do it any other way.
For the record, a tiny bit of sense is roughly how much I credit the WRG development team with.
Unfortunately there are times where different systems are incompatible or you decided to slowly migrate to a new DB and are left with legacy features using the old DB and new features using a new DB. Especially when you remember that portals are one of the oldest features in the game and need to support custom packs in addition to the general pack.
How WRG would design portal/voyage/retrieval today vs how they evolved over 6 years may be very different. I'm sure if they were all designed today they'd share the same DB flag. But I'm not convinced that a second column or duplicate list wasn't added over the years because it was easier/quicker when they were in a time crunch.
Except that Ben has been very clear that they're still dealing with the original code, database design etc. It's been a common theme in interviews where he gives the original design as a reason why some new feature can't be implemented, some design issue can't be fixed and so on. And they definitely don't have the development resource to start redeveloping from the ground up.
I mean, you're right in that the original design was obviously shoddy in so many ways. And if they were starting today, with the benefit of years of hindsight, I'm sure they'd do things differently. But the idea that you'd have two or three different ways of determining whether or not a crew is in the portal is just ludicrous. No rational human being would possibly code like that.
Sorry if this was mentioned before but couldn’t the crew confirmations be verified through looking at crew retrieval?
Absolutely they could. But where's the fun in that?
Only if you trust WRG to have retrieval and portal match with no bugs. Knowing the state of their code I wouldn't count on that.
As a reminder, the original reason these threads were created was because at one point TP said they made a portal update and then months later we realized the update was broken and the crew weren't in the portal. So now players look to verify each crew.
If we really wanted to be thorough we should have a separate 1-4* voyage confirmation check since it's possible a crew is added to portal and not voyages or vice versa.
I do actually trust WRG to have portal/voyages/retrieval all lined up. If only because driving it all off one database field is far and away the simplest option, coding it in any other way would be more complicated, require more work and frankly no software developer with even the tiniest bit of sense would do it any other way.
For the record, a tiny bit of sense is roughly how much I credit the WRG development team with.
Unfortunately there are times where different systems are incompatible or you decided to slowly migrate to a new DB and are left with legacy features using the old DB and new features using a new DB. Especially when you remember that portals are one of the oldest features in the game and need to support custom packs in addition to the general pack.
How WRG would design portal/voyage/retrieval today vs how they evolved over 6 years may be very different. I'm sure if they were all designed today they'd share the same DB flag. But I'm not convinced that a second column or duplicate list wasn't added over the years because it was easier/quicker when they were in a time crunch.
Except that Ben has been very clear that they're still dealing with the original code, database design etc. It's been a common theme in interviews where he gives the original design as a reason why some new feature can't be implemented, some design issue can't be fixed and so on. And they definitely don't have the development resource to start redeveloping from the ground up.
I mean, you're right in that the original design was obviously shoddy in so many ways. And if they were starting today, with the benefit of years of hindsight, I'm sure they'd do things differently. But the idea that you'd have two or three different ways of determining whether or not a crew is in the portal is just ludicrous. No rational human being would possibly code like that.
When I hear the original design and limitations, that's exactly why I don't trust that things are integrated. We know they had a bug in the portal release at one point. If the portal list was a hardcoded list of crew, then it may not be possible to use that same list for crew retrieval. When you think about how they need to support normal portals, tuesday packs, event packs, discount packs, etc... I can easily imagine there being a list of crew defined for each pack. How many times do we hear about mistakes/bugs in the crew available in the pack? I would hope crew retrieval is powered by a single flag on the crew data. But moving the portal to use that flag as opposed to a list tied to the pack is what I think about as a limitation in the original design and a challenge they need to overcome.
This is all speculation without seeing the code, but the term "tech debt" exists for a reason. And I would never assume software that has evolved over years is done in a logical way that you would design for given the current feature list.
All crew added with this update are now also available via Crew Retrieval as a result new constellations and polestars have been introduced to the game.
New Polestars Added
Dramen
Historian
Kobali
Kyrian
Photonic
Serpent
Tardigrade
Tellarite
Yaderan
CURRENTLY
"The truth is like a lion; you don't have to defend it. Let it loose; it will defend itself."
Prophet Kira from a basic single pull? I'd call that "Profit Kira"! Also, nice to see Hollow Engineer Zimmerman, Fencing Picard and Lieutenant Ogawa finally in the purrtal! Also, how is Gomtuu already in the purrtal?
"Everything about the Jem'Hadar is lethal!" - Eris (ST-DS9 Episode 2x26 "The Jem'Hadar")
All crew added with this update are now also available via Crew Retrieval as a result new constellations and polestars have been introduced to the game.
New Polestars Added
Dramen
Historian
Kobali
Kyrian
Photonic
Serpent
Tardigrade
Tellarite
Yaderan
CURRENTLY
"The truth is like a lion; you don't have to defend it. Let it loose; it will defend itself."
All crew added with this update are now also available via Crew Retrieval as a result new constellations and polestars have been introduced to the game.
New Polestars Added
Dramen
Historian
Kobali
Kyrian
Photonic
Serpent
Tardigrade
Tellarite
Yaderan
CURRENTLY
"The truth is like a lion; you don't have to defend it. Let it loose; it will defend itself."
Comments
Unfortunately there are times where different systems are incompatible or you decided to slowly migrate to a new DB and are left with legacy features using the old DB and new features using a new DB. Especially when you remember that portals are one of the oldest features in the game and need to support custom packs in addition to the general pack.
How WRG would design portal/voyage/retrieval today vs how they evolved over 6 years may be very different. I'm sure if they were all designed today they'd share the same DB flag. But I'm not convinced that a second column or duplicate list wasn't added over the years because it was easier/quicker when they were in a time crunch.
Except that Ben has been very clear that they're still dealing with the original code, database design etc. It's been a common theme in interviews where he gives the original design as a reason why some new feature can't be implemented, some design issue can't be fixed and so on. And they definitely don't have the development resource to start redeveloping from the ground up.
I mean, you're right in that the original design was obviously shoddy in so many ways. And if they were starting today, with the benefit of years of hindsight, I'm sure they'd do things differently. But the idea that you'd have two or three different ways of determining whether or not a crew is in the portal is just ludicrous. No rational human being would possibly code like that.
When I hear the original design and limitations, that's exactly why I don't trust that things are integrated. We know they had a bug in the portal release at one point. If the portal list was a hardcoded list of crew, then it may not be possible to use that same list for crew retrieval. When you think about how they need to support normal portals, tuesday packs, event packs, discount packs, etc... I can easily imagine there being a list of crew defined for each pack. How many times do we hear about mistakes/bugs in the crew available in the pack? I would hope crew retrieval is powered by a single flag on the crew data. But moving the portal to use that flag as opposed to a list tied to the pack is what I think about as a limitation in the original design and a challenge they need to overcome.
This is all speculation without seeing the code, but the term "tech debt" exists for a reason. And I would never assume software that has evolved over years is done in a logical way that you would design for given the current feature list.
I'm updating the list on page one. Since the person who did the last three sounded like they are ready for a break.
EDIT: Added
Lieutenant Sahil confirmed
Angela Martine confirmed
Profiteer Vash confirmed
CURRENTLY
CURRENTLY
CURRENTLY
Lt. JG Sam Lavelle
Kal'Hyah Sisko
Captain Burnham
Can also confirm the Romulan Bird of Prey.
Thanx! Using the full in-game name helps Scott find the right one a lot easier!
Updated to here.
¯\_(ツ)_/¯
ADDED
Can confirm Quarren of the Kyrian