I’m hoping to get some help with sharing my Twine project with a colleague. I want them to work on part of the story, but when I tried sending the generated .twee file, it didn’t seem to work—they couldn’t access the full project or make edits properly.
Could someone explain the best way to share a Twine project for collaborative work? Do I need to send more than just the .twee file? Are there specific folders or assets I should include? Any tips on ensuring my colleague can open, edit, and return the project without issues would be greatly appreciated!
Some sort of version-control, such as Git, Mercurial, etc. It is non-trivial but worth the learning-curve because of the benefits version-control brings.
Are they just proofing or actually writing code? There is a way to share a text only version, if that is the case. But then you would still need to make the edits yourself.
Otherwise, your colleague needs to have the same development environment that you’re using to write the game in. Are you using the desktop app?
The Poof proofing format by Chapel, perhaps?
Yes, I am using desktop app. Now I am trying to make him to use remote computer control to do his work on my development enviroment.
If you’re only wanting the other person to proofread and make comments, I’d consider Poof or Illume. If instead they are going to codevelop with you, then the way to go is Twee3 and source control.