Jump to content

Arrakus

Members
  • Content Count

    410
  • Joined

  • Last visited

About Arrakus

  • Rank
    Member

Recent Profile Visitors

988 profile views
  1. I am actually kinda OK with it. IMO, player character survivability is already at a disadvantage with how the game favors offense over defense. So I am willing to over look a suspect dev rulings in this particular case. Perhaps a disclaimer on the attachment. Some kind of GM beware. However... that could lead to a slippery slope. Food for thought.
  2. Since people are discussing data sets, I thought I would do a shameless plug. I help manage an open source data set. Will be two years come Aug. It is communitee driven/supported where members at any time can update any part of the data set. Crowd source maintanence. Link is in my profile bio.
  3. I host the data set on gitlab, not Github. And it is still there.
  4. I host the gitlab data set. We have seen this issue before. A fellow user went to great lengths to trouble shoot this error. Here is the link on the problem and the solution. https://gitlab.com/rikus01/SWDataSet-OggDudes/-/issues/3 I have reached out to Oggdude to see if there something within the program to fix it. Not sure if it was something that he could implement. In short: The error streams from how Windows zipps the file. People have had some luck using the .tar option when downloading the dataset. Others have had to rename the data set as follows : File name has to be named "SWDataSet-(NAME)" and first folder inside has to be "Dataset_(NAME)". Hope this helps.
  5. Thanks Oggdude. I GREATLY appreciate the help! Will let you know how it works.
  6. That is probably because I am doing a piss poor job of explaining it. Issue: The program will not import a data set if the first folder in the compressed file does not read "Dataset_(NAME)". If the first folder is not named "Dataset_(NAME)", then the program gives the following error: “This ZIP archive does not contain a valid Data Set” Occurrence: When compressing a data set by a program other than Data Editor, it is possible that the naming definition for the first folder in the compressed file will not read "Dataset_(NAME)". But instead will read “SWData*”. This will cause an error and the data set will not be able to be imported. Work Around: Manually rename the first folder in the compression file to "Dataset_(NAME)". Possible solution: Change the naming convention for the first folder in data set to match the naming convention for the compressed file, for example to “SWData*” Additional info: This naming requirement is not explained in the FAQ (Neither of them are). Making it difficult to figure out what the problem is and how to fix it.
  7. The dataset is at a hosted location, unzipped. Encountered the issue when downloading the dataset, compressed via ZIP and then attempting to import it. That is when we noticed file name format specifics. Unfortunately changing how the hosted location names the first folder inside the ZIP compression is challenging, at best. Is it possible to loosen or change those file name definitions? From "Dataset_<data set name>" to "Dataset*" Admittedly I am not a program; have no idea how plausible that maybe.
  8. Hey Oggdude, Was this below able to make it in to the patch? I did not see information relating to it in the notes. Would be helpful if it could. Thank you!
  9. I created an account over at Gitlab and have been maintaining a current data set (as current as one can be) over there. It has been up for about 3-4 months now, Link: https://gitlab.com/rikus01/SWDataSet-OggDudes Which would you rather do, the Google Groups that you have set up or this? I do not mind working with Gitlab project to keep it current.
  10. Hey Oggdude, This may be on of the more weird requests. Currently when importing a new data set, the compressed data set and the first folder inside the data set have to follow a specific naming convention. For example; the compressed file has to be named "SWDataSet-(*****)". While the first folder inside the data set also has to be named "Dataset_(*****)". The difference in the two naming conventions has caused some problems when sharing data sets between users. The naming convention for the compressed file is not an issue. However the naming convention for the first folder inside the data set is. Is it possible to either remove the naming convention restriction for the first folder inside the data set or make it so it matches the naming convention for the compressed data set. For example, both the file and folder have to be "SWDataSet-(*****)". Lastly, we have noticed we are unable to import data sets if that data set was compressed by Win10. However, if the data set was compressed with *.tar or *.rar, there are no issues. Not sure why that is.
  11. So is Sabine a sister looking for her brother, in search for her BFF or a love interest? Season 1 eluded to Ezra's attraction to Sabine, but in the final season it seemed more like a family/sister thing. However, in the epilogue she adopted his hair cut and was the only one out of the original crew who set off to find him (w/Ahsoka). Not that big of deal, but to me, it is interesting. Another thought, is it possible/feasible that Ahsoka is a live during Epi 7-9? She would be wicked old, but it *could* be possible.....
  12. That, and a hybrid twelick has no brain tails and human skin coloring?
  13. Higley doubtful. If Vader and Maul was able to instantly find a way off. Then so could have ahsoka.
  14. What I am curious to know is what Ahsoka did during the war. Since she was obviously around during it and was very much alive at the end of it. Curious to know if Yoda kept Ahsoka in the know about Luke or even trained her further.
×
×
  • Create New...