Utilities Quantum Console: The Ultimate in Game Development Console

Oh, okay cool.
So the challenge would be parsing an input field line by line into a list of commands which can then easily be passed into Quantum.

 

Hello- how would I print a list of my custom commands in the console?

In one of the demo videos you use "user-commands" and it prints a list of the user commands- I want to do exactly that- any tips? Thank you.

btw- I've disabled the built in commands

 

Take a look at the definition of the user-commands command inside of QuantumConsoleCommands.cs, should be clear from there if not, let me know

 

Got it! Thank you- great asset btw

 

Great! Glad you like it feel free to let me know if you need anything else or have any feedback, and if you have a moment a quick review goes a long way to helping out

 

V2.6.2 is now live, with a new custom scan rule system and optional parameters in command suggestions!

Full release notes here

 

Hi. I was wondering if my previous suggestion of being able to customize console initialize message? Like what if we want to change message like :

 

Unfortunately I haven't yet had time to add this although hopefully I can add it for the next update

 

Can you pop the console out into its own window or does it always have to run in the game view?

 

As in a completely separate window in your operating system? No Quantum Console doesn't provide anything like that for you

 

No, I want to doc the quantom console in another tab/view inside the unity editor. It looks like by default it runs in the game view which I dont want. Thanks for the quick reply.

 

The included UI/interface is designed as an in game console and not an editor extension, so no out of the box you can't run the UI as an editor extension

That said, most of the functionality of QC isn't handled inside of the UI so you could most likely write an editor extension interface but it wouldn't be trivial to get all the features like autocomplete working

 

@castor76 Quantum Console V2.6.3 has just been released which includes your feature request for customisable localization!

 

Thanks will give it a go. Is there doc on how to do that?

 

Yep - https://www.qfsw.co.uk/docs/QC/articles/quickstart/localization.html

 

Thanks.. But I need to update the package to the 2.6.2.. is there any free update to the previous version user?

 

Depends on when you purchased QC originally - if you purchased it less than a year before V2.6 was released, then the upgrade is completely free; if it was more than a year before then the upgrade fee is heavily discounted

 

Ok, is this reflected on my asset store page then? It seems to be $10

 

Yes, just make sure you're logged in. $10 would be the discounted fee

 

No problem, thanks for letting me know.

 

is it can be used for mobile too?

 

Yep! You'll probably want to add a button to your UI somewhere for opening the console

 

Quantum Console V2.6.4 is now live! Some standout features

• Autocompletion works much better now when suggestions contain whitespace
• New `ReadLine` and `ReadValue` actions for getting user input during a command thanks to @Monsoonexe

Full patch notes here as always

 

Quantum Console V2.6.5 is now live!

I've made two new MonoTargetTypes,

Argument

/

ArgumentMulti 

that let you provide the target(s) as the first argument to the command. This is basically an automatic version of the old "make a static command that dispatches to the target" trick so should be very convenient!

 

I've launched the first version of Made with QC, a showcase of a few of the awesome games that have been made with Quantum Console! Check out everyone's great work here
https://www.qfsw.co.uk/docs/QC/articles/showcase/showcase.html

If you're working on something with Quantum Console, please share I'm always excited to see what people are using it for

 

Hi QFSW,

is it possible for you to wrap the current QC_DISABLED* preprocessors around the actual source code of Quantum Console?

I am a bit concerned about people who want to manipulate the release build. With the current implementation, they would simply need to override one simple check in QuantumConsole.cs to be able to access the full console with all the features - even if it was disabled with the preprocessor.

 

Tried changing the toggle key from escape to tilde also known as the key to the left of the 1. `
For whatever reason Quantum console doesn't like using that key and I have to manually toggle it with my own script. on ` press.

 

Hi @WongKit

While I agree with you on a fundamental basis, it's unfortunately not that simple. I can't wrap _all_ the code in the preprocessor, as putting serialized fields inside of the preprocessor causes build errors. Because of this I would have to wrap most of the code in it, but then provide empty fallbacks for the unwrapped code. This would work, but it's easy for things to go wrong and I've decided it's not currently worth the maintenance cost

One idea if you want to make your game safer - you could have your QC prefab in an asset bundle inside of in the scene, then you only include the asset bundle (and said loading code) in builds where you want to include QC. This way, even with code modifications, there won't be any easy way to actually add the console in. (I'm aware that this can still be worked around, but at this point it would be similar to modding QC into the game in the first place)

 

It may be that the ` key is actually somewhere else on your keyboard based on a layout mismatch. Try ~ instead

 

Thank you for your reply! I agree, that it is not feasible to wrap *everything* in the preprocessor, but what about only defusing the commands in QFSW.QC.Extras namespace? Those are the most versatile (dangerous ) commands that could be used to manipulate the runtime player. Wrapping them should not produce any build errors as they would be called dynamically anyway.

I am fully aware, that someone who wants to tamper with an application will find other ways to do so. It is more about not providing easier entry points. Btw, I would not even mind, if someone would be able to show/load the console when it is only capable of viewing the logs. As I am already wrapping my custom commands in preprocessor conditions, they could never be run from a release build.

 

That sounds like a good compromise to me! Disabling them is high value, low maintenance. Will do this for the next release of QC