Slitherine

quote:

Frankly if I could take them all down and have Steam users use the normal version of the CSP it would be a lot less of a headache.

quote:

ORIGINAL: rixtertech

quote:

Frankly if I could take them all down and have Steam users use the normal version of the CSP it would be a lot less of a headache.

@Kushan04, this is an interesting comment. Are you saying that we -can- simply download the standalone CSP and extract it into the Steam-install scenario directory? This would be ideal if it will work. I'd love to have all the scens working with the new DB's. Has anyone tried this succesfully or does Steam have a canary when it sees the alien content?

quote:

ORIGINAL: jarraya
Hi all, what's happened with the Community Scenario Pack? Has it been superseded by Steam now?

quote:

ORIGINAL: rixtertech
Installing the CSP into my steam scn directory worked nicely... you may want to change the line in your top post that states "Sorry Steam users but you only get the new scenarios and the 9 updated scenarios updated to the latest DBs" into a hopefully clearer statement such as...

"Steam users can ensure that all of their CSP scenarios use the latest DB's by downloading the standalone CSP and extracting into their Steam client CMO scenario directory. The zip extraction will create a folder named 'Community' or you can use a new folder name of your choice. You will also want to extract the contents of the 'Lua' folder into your 'Lua' directory in the steam install. Do not just overwrite the Lua directory, as it may already contain other files."

quote:

ORIGINAL: Kushan04

quote:

ORIGINAL: rixtertech
Installing the CSP into my steam scn directory worked nicely... you may want to change the line in your top post that states "Sorry Steam users but you only get the new scenarios and the 9 updated scenarios updated to the latest DBs" into a hopefully clearer statement such as...

"Steam users can ensure that all of their CSP scenarios use the latest DB's by downloading the standalone CSP and extracting into their Steam client CMO scenario directory. The zip extraction will create a folder named 'Community' or you can use a new folder name of your choice. You will also want to extract the contents of the 'Lua' folder into your 'Lua' directory in the steam install. Do not just overwrite the Lua directory, as it may already contain other files."

Some big changes to CSP 45 in regards to Steam. One of the other devs has given me a utility that can either update multiple scenarios at the same time OR (in my personal opinion the most exciting part) upload multiple scenarios as a single entity download. What I'll be doing for CSP 45, is removing all of the individual scenarios from Steam, and converting them to the single download.

I'll be updating that single entity going forward. Once you subscribe to it, that should be it. There will no longer be the need to go and subscribe to each individual CSP scenario in the collection when I update the pack, plus you'll get all the scenario updates. Another major advantage of this is you will get all the scenario documents and attachments. Although because its Steam, they will get placed in your Steam workshop folder and not the Command installation folder.

Currently aiming to release CSP 45 the first week of November.

quote:

ORIGINAL: BobTank63

quote:

ORIGINAL: Kushan04

quote:

ORIGINAL: rixtertech
Installing the CSP into my steam scn directory worked nicely... you may want to change the line in your top post that states "Sorry Steam users but you only get the new scenarios and the 9 updated scenarios updated to the latest DBs" into a hopefully clearer statement such as...

"Steam users can ensure that all of their CSP scenarios use the latest DB's by downloading the standalone CSP and extracting into their Steam client CMO scenario directory. The zip extraction will create a folder named 'Community' or you can use a new folder name of your choice. You will also want to extract the contents of the 'Lua' folder into your 'Lua' directory in the steam install. Do not just overwrite the Lua directory, as it may already contain other files."

Some big changes to CSP 45 in regards to Steam. One of the other devs has given me a utility that can either update multiple scenarios at the same time OR (in my personal opinion the most exciting part) upload multiple scenarios as a single entity download. What I'll be doing for CSP 45, is removing all of the individual scenarios from Steam, and converting them to the single download.

I'll be updating that single entity going forward. Once you subscribe to it, that should be it. There will no longer be the need to go and subscribe to each individual CSP scenario in the collection when I update the pack, plus you'll get all the scenario updates. Another major advantage of this is you will get all the scenario documents and attachments. Although because its Steam, they will get placed in your Steam workshop folder and not the Command installation folder.

Currently aiming to release CSP 45 the first week of November.

Does this mean that there will be no difference between the Steam and Standalone CSP?

quote:

ORIGINAL: boogabooga

I want to mention that the Lua folder that comes in the CSP needs to be moved to the main game directory and is useless if it stays in the Scenario directory. This is true for both standalone and Steam. The'GulfofSidra1981' folder needs to end up there with all of the other Lua folders from the stand-alone scenarios or else the the Gulf of Sidra, 1981 scenario will not work properly. AFAIK, that's the only way to get the scripts to work. Apparently, I'm the only one in the CSP that is using separate Lua scripts. (Oops)

This is probably going to be an issue for Steam users, since the location of the Lua folder that needs to be moved is rather obscure.

quote:

ORIGINAL: RFalvo69

After a few months playing other games I just reinstalled a fresh copy of Command - after ensuring that no leftovers remained in the Steam folder (I have Command on Steam). What happens is this:

- If I install Command, Steam automatically installs about 70MB of "Steam Commons Redistributables". When I check the "Steam Workshop" label in the scenario list I find the scenarios of the Community Pack - or at least a version of them.

- If I then install the Community Pack via the Steam Workshop, I find A LOT of duplicates in the list. By then I don't know anymore which the most recent version of a given scenario is.

So, what should I do? Accept the Community Pack which is automatically installed by the SCR, download the Workshop version and check which file is the most recent one (a chore with 500+ scenarios) or what?

quote:

ORIGINAL: Kushan04

quote:

ORIGINAL: RFalvo69

After a few months playing other games I just reinstalled a fresh copy of Command - after ensuring that no leftovers remained in the Steam folder (I have Command on Steam). What happens is this:

- If I install Command, Steam automatically installs about 70MB of "Steam Commons Redistributables". When I check the "Steam Workshop" label in the scenario list I find the scenarios of the Community Pack - or at least a version of them.

- If I then install the Community Pack via the Steam Workshop, I find A LOT of duplicates in the list. By then I don't know anymore which the most recent version of a given scenario is.

So, what should I do? Accept the Community Pack which is automatically installed by the SCR, download the Workshop version and check which file is the most recent one (a chore with 500+ scenarios) or what?

You're probably still subscribed to the old CSP scenarios that Baloogan uploaded to Steam before I took over maintaining it. Best way would be to go to Command Workshop -> Your Subscribed Items and then select the "Unsubscribe From All" button then resubscribe to the official CSP from the link in the first post of this thread.

quote:

ORIGINAL: Kushan04

quote:

ORIGINAL: boogabooga

I want to mention that the Lua folder that comes in the CSP needs to be moved to the main game directory and is useless if it stays in the Scenario directory. This is true for both standalone and Steam. The'GulfofSidra1981' folder needs to end up there with all of the other Lua folders from the stand-alone scenarios or else the the Gulf of Sidra, 1981 scenario will not work properly. AFAIK, that's the only way to get the scripts to work. Apparently, I'm the only one in the CSP that is using separate Lua scripts. (Oops)

This is probably going to be an issue for Steam users, since the location of the Lua folder that needs to be moved is rather obscure.

There are a few official scenarios that call external scripts but yeah most just copy the entire script into the lua event action.

Would it be ok with you if I modify the scenario to add those scripts directly into the scenario so the folder would not be needed? Wouldn't make another other changes.