-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension Fails To Detect Scripts Folder #40
Comments
Seems the extension cannot find .zsrc file. That's the key of most features provided by this extension. |
I'm still somewhat of a ZenScript newbie - this is my first time ever hearing of .zsrc files! Is there any good resource to go to that explains their purpose? I find a lot of ZS documentations to be somewhat..difficult compared to standard programming documentation. |
The purpose of generating such a file is to dump information from the game to the disk, so that information in game can be used without launching Minecraft every time you want to write ZS scripts. For example, items are only accessible in game. If you want to add a recipe to, for example, If ZenScript is actually not well-documented compared to other programming languages. A good way to learn ZenScript is to read scripts written by other modpackers(learn by example). Most modpacks follow this pattern: create one file for each mod and modify recipes of that mod in the file. SevTech creaters used another pattern: they write ZenScript like Java, taking great advantage of classes and callbacks in this language. |
Wow, thank you for explaining all this with such clarity! This will definitely aid the development process of this modpack I'm working on. |
Hi Yesterday, After generating the .zsrc file, the plugin works as expected. Should I close the issue now, or would you prefer it remain open as a reminder to work on some things? Thanks for your time! |
Just keep it open. Waiting for a reproducible example when others meet the
same problem :)
Brittank88 <[email protected]> 于2021年1月19日周二 下午1:37写道:
… Hi Yesterday,
After generating the .zsrc file, the plugin works as expected. Should I
close the issue now, or would you prefer it remain open as a reminder to
work on some things?
Thanks for your time!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#40 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCEFLRRQ7SGGTM4HSTXMSTS2ULAXANCNFSM4WAI7DWA>
.
|
Hey! I'm having this same issue, but when I put the "probe" folder in my mods folder it does not generate the .zsrc file. what do I do? |
@asdfghjkl403622 Could you please describe how did you use probe and this extension step by step? |
@Yesterday17 I suggest you change the message a little. (Maybe even hint that a mod is missing) |
@jeengbe sure.. the hint now seems confusing |
I too was left wondering what to do with the Probe mod. You might want to include some quick instructions on what to do with the Probe mod. ie:
|
Hello, I am trying to figure out what went wrong. I used the mod Can I get more details on how it works? like does the VSCode have to have a workspace which is within the scripts folder, not the root of the Minecraft directory? edit: |
Hi there! I am having an issue whereby this extension refuses to detect that I have the scripts folder open as my workspace:
Not sure what else to do from here - I've tried running VSCode with administrator privileges, and that .minecraft folder setting appears to no longer exist...
The text was updated successfully, but these errors were encountered: