Dr_Romantic

Should this one be handled with getting version of current server, like if(version > 1160){ //use hex if string have } else { //use defualt color code }

# New CommandTrigger option ## `runnable_in_console: true/false` This option saved in `trigger.json` , as `runnable_in_console: true/false` . If true, the command trigger would be available for ConsoleCommandSender. If false, only...

I think it would be great if we use ${} logic. We already parsing ${something} inside a string as $something(Placeholder), which is not that welcome-d (at least for me) because...

The Customized Tab completion logic looks great for me, but with that logic, there would be one weak part which could be major problem for users. **'arg-arg Interaction'** Most user...

@wysohn Let me use a system that I maid as an example. on CommandTrigger ``` IF args.length == 0 #CALL "AutoChestHelp" false ELSE operation = args[0] IF operation.equalsIgnoreCase("check") && args.length...

@wysohn It looks great, yet I'm not really sure why args must be *consumed* from args which actually makes user hard to use pre-comsumed arguments. As you can see in...

@wysohn Sorry for late replying. I was really busy these three days 'bout graduation problem. Anyway, I may agree that using Queue is better way to handling List by the...

commits: c293724 , 479fbcc New Command Trigger Tab-Completion Model Suggestion Command Usage **NOT YET IMPLEMENTED** JSON Tested and Fully functional on - [x] Bukkit-latest - [ ] Bukkit-legacy - [...

@soshimee > I feel like the ability to disable tab-completion completely (like on older versions of TriggerReactor) is a good idea as well. I'll look into it. But, for me,...

@Sayakie > I assume this feature should be bumped to 3.4.x, not to 3.3.x Hmm, I thought adding this feature on 3.3.0 would be best option because 1. current model(old...