You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy and pasting the exact example used in the manual
I - Instance Create:instance_create_layer(x, y, |layer|, object);
will cause this to pop up when GM is started:
Checking the text file again after hitting yes, it will show this
Instance Create:instance_create_layer(x, y, |layer|, object);
The snippet will still be linked to the I key properly in the IDE, but there's now no clear way to edit what key the snippet is bound to. Whatever the new way is, it should be in the documentation.
In addition, the location listed in the manual to create the text file is %ProgramData%\GameMaker\User, but the folder is actually called GameMakerStudio2 instead of just GameMaker.
Remove the binding from the snippets example, in this case the leading I -
Mention that any custom snippets added will have an unbound hotkey created for them
Mention that these hotkeys can be remapped like any other through the Preferences -> Redefine Keys menu
Replace the example screenshot at the bottom, which contains out-of-date default snippets. These snippets no longer have bindings, as they are specified through the usual hotkeys files
Description
Copy and pasting the exact example used in the manual
will cause this to pop up when GM is started:
Checking the text file again after hitting yes, it will show this
The snippet will still be linked to the I key properly in the IDE, but there's now no clear way to edit what key the snippet is bound to. Whatever the new way is, it should be in the documentation.
In addition, the location listed in the manual to create the text file is %ProgramData%\GameMaker\User, but the folder is actually called GameMakerStudio2 instead of just GameMaker.
Manual Link
https://manual.gamemaker.io/monthly/en/index.htm#t=The_Asset_Editors%2FCode_Editor_Properties%2FCode_Snippets.htm
The text was updated successfully, but these errors were encountered: