fixed GCS import for v4, moved actor import to separate file

ReleaseProcess.md

@@ -7,11 +7,11 @@ Make certain "main" branch is up to date with the latest features, and commit.
 Check out the "release" branch
 
     git checkout release
-    
+
 Merge in the "main" branch
 
     git merge main
-    
+
 Edit the following files:
 
 README.md - Change the release version
@@ -20,24 +20,24 @@ changelog.md - Add the date of the release
 
 system.json -
 
-  Change the version
-  
+Change the version
+
     "version": "0.17.2"
-  
-  NOTE:   Do NOT prefix a number with zero (0).   "0.17.02" will cause problems later.
-  
-  Update the compatibility, if necessary:
-  
+
+NOTE: Do NOT prefix a number with zero (0). "0.17.02" will cause problems later.
+
+Update the compatibility, if necessary:
+
     "compatibility": {
       "minimum": "12",
       "verified": "12.324"
     },
-    
-  Update the download (Use the exact same version string as the ZIP file name prefix):
-  
+
+Update the download (Use the exact same version string as the ZIP file name prefix):
+
     "download": "https://github.com/crnormand/gurps/archive/0.17.2.zip",
-  
-Commit as the version "0.17.2" and push.   Although the commit tag isn't as important.
+
+Commit as the version "0.17.2" and push. Although the commit tag isn't as important.
 If you messed up something, you can fix and recommit as a different tag.
 I usually go with something like "0.17.2b".
 
@@ -48,13 +48,14 @@ Checkout "main" and update
     git push
 
 # On GitHub
+
 Click on "**Releases**"
 
 Then "**Draft a new release**"
 
 Click on "**Choose a tag**" and create a new tag, using the exact same version string "0.17.2".
 
-As we have found out... you must NOT prefix number with zero.  Example:  "0.17.02".
+As we have found out... you must NOT prefix number with zero. Example: "0.17.02".
 
 Click on "**Target: main**" and select the "release" branch.
 
@@ -64,7 +65,6 @@ Paste the changelog enrties into the "Describe this release" text area.
 
 Click "**Public release**".
 
-Let me know that you have created a new release.   I need to update the Foundry website.
-
-NOTE: Existing customers will be able to upgrade to the new release immediately.    New customers will get the version identified on the Foundry website.
+Let me know that you have created a new release. I need to update the Foundry website.
 
+NOTE: Existing customers will be able to upgrade to the new release immediately. New customers will get the version identified on the Foundry website.

changelog.md

@@ -6,34 +6,34 @@ Release 0.17.6
 - Fixed Physical Dice roll
 - Fixed Resource Tracker display (esp for Control Points)
 - Fixed setting 'dead' status from combat tracker
-- Fixed Target Range (in Effects Modifier), when scene grid is NOT yards 
+- Fixed Target Range (in Effects Modifier), when scene grid is NOT yards
 
 Release 0.17.5
 
 - Add CSS to enable horizontal scrollbars if the width of the window is less than the width of the actor sheet.
 
-Release 0.17.4  6/29/2024
+Release 0.17.4 6/29/2024
 
 - Dice So Nice now works for most targetted rolls and damage. This appears to also fix the public/private/blind chat messages.
 - Fix Shock and Major Wound errors when clicked on in the chat.
-  
-Release 0.17.3  6/19/2024
+
+Release 0.17.3 6/19/2024
 
 - Update 'duplicate' method (deprecated) to 'foundry.utils.duplicate'.
 - Fix problem where Tracker value was being treated as a string.
 - Fix Resource Trackers not updating.
 - Fix setting Maneuvers on actors in combat.
 - Fix right side truncation of default GCS sheet with PopOut! (It still opens the width of your monitor, though.)
 
-Release 0.17.2  6/03/2024
+Release 0.17.2 6/03/2024
 
 - Fix merge issue
 
-Release 0.17.1  6/03/2024
+Release 0.17.1 6/03/2024
 
 - Fix version number issue
 
-Release 0.17.0  6/02/2024
+Release 0.17.0 6/02/2024
 
 - Update for Foundry V12
 - Update for JB2A v0.6.8