-
Notifications
You must be signed in to change notification settings - Fork 165
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
.lang file intellisense error[BUG] #457
Labels
Bug
Something isn't working
Comments
Thank you for reporting this I'll make sure this is fixed in 2.8 |
Thank you :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Whenever I need to update a .lang file in a resource pack to add a name to an item I made, the intellisense doesn't allow me to autocomplete it correctly. It will give me the option to autocomplete it correctly once type an underscore character (
_
), it'll act like I typed a few wrong characters, and insert the whole thing after the characters in the namespace I typed, or something like that. It's also generally finicky.To Reproduce
Steps to reproduce the behavior:
my_blank_item
. Anything will work however (or not work? lol)example:my_blank_item
for this.en-US.lang
file and begin to type in (not copy/paste)item.example:my_blank_item=Whatever
. The intellisense will be kind of strange.item.my_n
The intellisense will read: item.example:my_blank_item. Press tab or enter. You will now have:item.example:my_item.example:my_blank_item
Observed behavior
This has happened for me multiple times when I was developing a mod that had a lot of items in it.
Expected behavior
I expected the intellisense to kick in right away with the correct option to autocomplete, and not just start all over again on the beginning of the name.
Screenshots / File Attachments
Platform (please complete the following information):
Additional context
This is just one example of how .lang file intellisense is weird. Sometimes it just doesn't work entirely.
The text was updated successfully, but these errors were encountered: