AntiMatter_16 on 17/8/2014 at 19:03
I would say so. I haven't encountered any bugs in my testing, and haven't received any reports.
Nameless Voice on 18/8/2014 at 17:16
Came here to post this.
Found myself late to the party.
DJ Riff on 19/8/2014 at 16:35
At least not too late to be included in Tafferpatcher.
BTW, is there a foolproof tool to create a BMP texture out of TTF font file to be suitable for Font Tool?
AntiMatter_16 on 6/12/2014 at 23:48
Minor update, DromEd & ShockEd Basic updated to version 1.13. See the Original Post for download links.
Changes:
Added "Particle Color Palette.jpg" to docs
Added "Draw Link type..." and "Hide Link type..." to Show/Hide submenu
Added New EAX values (22-25) to EAX menu
Added "Reorder Scripts..." to Script submenu
R Soul on 9/2/2015 at 21:49
Why have you set alt+e to run unset editorcam_from_game before running edit_mode (EditMode.cmd)?
editorcam_from_game goes in user.cfg, and once there alt+e only needs to run the edit_mode command. Unsetting editorcam... means the camera will return to the starting point when returning to Dromed.
This probably won't affect people with existing installations because updated Dromed keybinds (from Default.bnd) won't get written to cfg#.bnd (and then user.bnd) if existing keybinds are already there. However I installed from scratch with Tafferpatcher, which uses this toolkit, and one of the first things I did was to go in game and re-set my T2 keybinds. This set alt+e to run EditMode.cmd. It's not hard to undo this with just one cfg#.bnd, but there are still three files to edit.
AntiMatter_16 on 10/2/2015 at 00:26
Because...
Alt+R returns to Edit Mode at the point you were in game mode.
Alt+E returns to Edit Mode at the point where you entered game mode (if persistent_player_pos is set or at the starting point if it is not).
