-
Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.
If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.
- The Lone Wolf Development Team
Best way to run Realm Works on multiple computers
- Thread starter Majorian
- Start date
I don't use anything like Realm Works anymore...
But the paid thing lets you sync between devices.
I basically would do preparation on the desktop at home.
Then sync to the laptop that would come to the gaming.
Sync any changes made there back to the cloud.
Then sycn the desktop back to current and do whatever.
The process is about the same now.
But I'm not using anything like RW.
Both the desktop and laptop point to the same Dropbox folder.
The path is a little different, but it is similar.
I have the VTT there, so I can prep maps and monsters.
I have files called... Session 038 (was what I used today).
I'll make a Session 039 based off of 038 sometime before next week's game.
The campaign is more text files now and 2-3 documents for what it going on.
It isn't linked like RW was.
But it works.
But the paid thing lets you sync between devices.
I basically would do preparation on the desktop at home.
Then sync to the laptop that would come to the gaming.
Sync any changes made there back to the cloud.
Then sycn the desktop back to current and do whatever.
The process is about the same now.
But I'm not using anything like RW.
Both the desktop and laptop point to the same Dropbox folder.
The path is a little different, but it is similar.
I have the VTT there, so I can prep maps and monsters.
I have files called... Session 038 (was what I used today).
I'll make a Session 039 based off of 038 sometime before next week's game.
The campaign is more text files now and 2-3 documents for what it going on.
It isn't linked like RW was.
But it works.
buyhighdapbn
New member
The main goal of the paid service is to facilitate this process. Alternatively, you can back up the database on one machine, transfer the file, and then restore it on the other using the Tools page of the launcher.
Powershell
I just had Copilot do this for me
Nice little script that you can run each time you make changes and have it save to OneDrive or similar without having to think too much.
powershell
Copy code
# Define the source and destination folder paths
$sourceFolder = "C:\SourceFolder"
$destinationFolder = "C:\DestinationFolder"
# Check if the source folder exists
if(!(Test-Path $sourceFolder)){
Write-Host "Source folder does not exist."
exit
}
# Check if the destination folder exists
if(!(Test-Path $destinationFolder)){
Write-Host "Destination folder does not exist. Creating destination folder."
New-Item -ItemType Directory -Path $destinationFolder | Out-Null
}
# Get the current contents of the source folder
$sourceFiles = Get-ChildItem $sourceFolder -Recurse
# Get the contents of the destination folder
$destinationFiles = Get-ChildItem $destinationFolder -Recurse
# Compare the contents of the source and destination folders
$filesToCopy = Compare-Object $sourceFiles $destinationFiles -Property Name, Length -PassThru | Where-Object {$_.SideIndicator -eq "<="}
# Copy the files to the destination folder if there are changes
if($filesToCopy){
Write-Host "Copying files to destination folder."
Copy-Item $filesToCopy.FullName -Destination $destinationFolder -Force
}
else{
Write-Host "No changes detected."
}
This script first defines the source and destination folder paths. It then checks if the source folder exists and exits the script if it doesn't. Next, it checks if the destination folder exists and creates it if it doesn't.
The script then gets the current contents of the source folder and the contents of the destination folder. It compares the contents of the two folders based on the file name and length using the Compare-Object cmdlet and stores any files that are in the source folder but not the destination folder in the $filesToCopy variable.
Finally, if there are changes detected, the script copies the files to the destination folder using the Copy-Item cmdlet. If there are no changes detected, it outputs a message saying so.
I just had Copilot do this for me
Nice little script that you can run each time you make changes and have it save to OneDrive or similar without having to think too much.
powershell
Copy code
# Define the source and destination folder paths
$sourceFolder = "C:\SourceFolder"
$destinationFolder = "C:\DestinationFolder"
# Check if the source folder exists
if(!(Test-Path $sourceFolder)){
Write-Host "Source folder does not exist."
exit
}
# Check if the destination folder exists
if(!(Test-Path $destinationFolder)){
Write-Host "Destination folder does not exist. Creating destination folder."
New-Item -ItemType Directory -Path $destinationFolder | Out-Null
}
# Get the current contents of the source folder
$sourceFiles = Get-ChildItem $sourceFolder -Recurse
# Get the contents of the destination folder
$destinationFiles = Get-ChildItem $destinationFolder -Recurse
# Compare the contents of the source and destination folders
$filesToCopy = Compare-Object $sourceFiles $destinationFiles -Property Name, Length -PassThru | Where-Object {$_.SideIndicator -eq "<="}
# Copy the files to the destination folder if there are changes
if($filesToCopy){
Write-Host "Copying files to destination folder."
Copy-Item $filesToCopy.FullName -Destination $destinationFolder -Force
}
else{
Write-Host "No changes detected."
}
This script first defines the source and destination folder paths. It then checks if the source folder exists and exits the script if it doesn't. Next, it checks if the destination folder exists and creates it if it doesn't.
The script then gets the current contents of the source folder and the contents of the destination folder. It compares the contents of the two folders based on the file name and length using the Compare-Object cmdlet and stores any files that are in the source folder but not the destination folder in the $filesToCopy variable.
Finally, if there are changes detected, the script copies the files to the destination folder using the Copy-Item cmdlet. If there are no changes detected, it outputs a message saying so.