Writing code is so much more enjoyable when you have tools to help you out. Integrated Development Environments do a good job of providing helpful tools, but running a separate IDE alongside Gamecraft is resource-intensive and the IDE won't be able to provide important GC-specific tooling.
To get the best of both worlds, GamecraftScripting should have an IDE built in.
In my opinion, the most important tools to have are:
Looking at block (id, type, colour, position, signal info)
Block in hand (type)
Active mods (list of name, version)
Writing code is so much more enjoyable when you have tools to help you out. Integrated Development Environments do a good job of providing helpful tools, but running a separate IDE alongside Gamecraft is resource-intensive and the IDE won't be able to provide important GC-specific tooling.
To get the best of both worlds, GamecraftScripting should have an IDE built in.
In my opinion, the most important tools to have are:
- Text editor\*
- Extended debug info\*
- (done) Descriptive Python error messages
- GamecraftModding API reference (like to https://api.exmods.org at least)
Text Editor specifics:
- Overlay UI for text entry
- Use text blocks?
- Python autocomplete
- GamecraftModdingAPI autocomplete
Extended Debug Info specifics (in F3 menu):
- Currently executing script
- Python version info
- Looking at block (id, type, colour, position, signal info)
- Block in hand (type)
- Active mods (list of name, version)
NGnius
added this to the v1.0 milestone 4 years ago
Writing code is so much more enjoyable when you have tools to help you out. Integrated Development Environments do a good job of providing helpful tools, but running a separate IDE alongside Gamecraft is resource-intensive and the IDE won't be able to provide important GC-specific tooling.
To get the best of both worlds, GamecraftScripting should have an IDE built in. In my opinion, the most important tools to have are:
Text Editor specifics:
Extended Debug Info specifics (in F3 menu):