|
#1
|
|||
|
|||
Modding console / debugger
Short and simple (?) question
Is there any way a console (or similar) can be used to show typos or syntax errors in mods? Just something as simple as "File: mod_test.gdb not loaded - syntax error" would be a step in the right direction. The modding environment in this game is amongst the simplest I have encountered (so big kudos to the dev there!) but I am still doing silly mistakes.. so any clever tricks? (other than proofreading syntax ) |
#2
|
||||
|
||||
If you look in the console (~ key), it will show you some errors, but most of the time you are going to need to be careful and not make mistakes.
__________________
Steven Peeler Designer/programmer Depths of Peril, Kivi's Underworld, Din's Curse, Drox Operative, Zombasite, Din's Legacy, Drox Operative 2, & Din's Champion Wishlist Din's Champion |
#3
|
|||
|
|||
Quote:
Anyway, in a danger of turning this into a bit of "quiz the dev" The file Hulls.gdb has entires like Code:
Name $$HullName2$$ |
#4
|
||||
|
||||
The $$ stuff means it's going through the localization/translation stuff. In this case, HullName2 is an entry in Loc/English/items.trn
Mods don't need to go through the localization stuff though. Just Replace $$HullName2$$ with whatever your new name is. If it has a space in the name it will need "" around the name though.
__________________
Steven Peeler Designer/programmer Depths of Peril, Kivi's Underworld, Din's Curse, Drox Operative, Zombasite, Din's Legacy, Drox Operative 2, & Din's Champion Wishlist Din's Champion |
#5
|
|||
|
|||
Great! Thanks
|
Thread Tools | |
Display Modes | |
|
|