29.08.2019
85
Scp Cb Old Versions 3,5/5 186 reviews
Scp cb old versions full
The rich text editor does not work with JavaScript switched off. Please either enable it in your browser options, or visit your preferences to switch to the old MediaWiki editor
  • Hi I want to know which is the best (and most stable) scp cb version. I was playing version 6.3 but then 6.5 came out but my savegame from 6.3 did not work on 6.5. Will this game ever be stable. What do you reccoment? I think I'm close to beat the 6.3 version of the game. should I beat all of the versions that keep being released. or wait for a stable, full version of the game. I'm kind of confused with all these versions.

    Loading editor
    • there will never be a 'stable full' version of the game. The only way that would happen is if the author of the game decided to recode the game entirely using a different, less shitty game engine. Blitz3d sucks really, really badly, and you should just beat the game, then revisit it when you see any significant changes in the changelog.

      Loading editor
    • 0.6.6 is in my opinion the last stable version of CB, and even then it was still kinda buggy.

      Loading editor
    • 71.46.81.59 wrote:
      there will never be a 'stable full' version of the game. The only way that would happen is if the author of the game decided to recode the game entirely using a different, less shitty game engine. Blitz3d sucks really, really badly, and you should just beat the game, then revisit it when you see any significant changes in the changelog.


      Ok, thanks for the information, I'm going to do what you suggested.


      Loading editor
    • 70.29.236.195 wrote:
      0.6.6 is in my opinion the last stable version of CB, and even then it was still kinda buggy.

      I'll try it. Thanks.

      Loading editor
    • Loading editor
    • Topics for this thread:

I actually have, and will continue, to keep every released version of SCP:CB on my computer. Interesting thing though, when I replayed the first version I discovered some of the rooms from later versions were being generated, mainly it was the maintenance tunnel.

  1. Jun 4, 2018 - SCP Containment Breach old versions and 1.3.9, includes SCP Nine Tail Fox mod.Requires 1.2 version (see moddb page for more info about.
  2. Improved versions of the old door sounds The correct sounds are now played when opening/closing the large containment doors Random sound clips (distant gunfire, screams etc) are played for a short period of time after the intro. SCP CB version 3.11 A FANDOM user.
Retrieved from 'https://containmentbreach.fandom.com/wiki/Thread:8093'
Community content is available under CC-BY-SA unless otherwise noted.
Old
  • Status:Resolved(View Workflow)
  • Resolution: Answered
  • Fix Version/s: None
  • Labels:
  • Last commented by user?:
  • Comments:
  • Bug Fix Policy:

I have an issue with a scp copy job copying artifacts to a remote system. It seems to work correctly (as in build stage creates a valid artifact, deploy stage references that artifact) but executes the actual copying of the artifact twice (one with the current version of the artifact, once with an older version of the artifact). This results in my freshly compiled and packaged application being replaced with a version from a previous build, which is a problem.)

Strangely the artifact-link is correctly offered in the bamboo webapp, It also looks fine from the file structure view of the build-stage, just when the deploy-stage begins it seems to copy the current and an old version of the artifact to the working directory and then proceeds to scp both files to the remote location.

Here is the relevant part of the log:

As you can see there are two files beeing copied to the remote server: the first file is the current product of the build, the second one is the 'old', deprecated file.

please advise, what can i do, where can i look?

Scp Cb 0.1

  • Assignee:
    Unassigned
    Reporter:
    Sebastian Hilder
    Participants:
  • Votes:
    2Vote for this issue
    Watchers:
    5Start watching this issue
  • Created:
    Updated:
    Resolved:
    Last commented:
    3 years, 37 weeks, 3 days ago