brakeys is better

@@jgoglescu You can think that way if you want.

@@jgoglescu No One Asked

@@PhodexGames bEtTeR tHaN bRaCkeYs. Like who the fk are u niqqa

@@uxdecipher1724 Definetly not a niqqa lol.

Can you share your project? If it just a recreation of course.

@@vantinhnong2206 i didn't get to implement any version I find, i measure the tutorial by how complicated the code is and how good does the tutorial guy explain it

@@Pedro_Marangon These tutorials are so great but its creator forgot to put it on Github, really sad!

@@vantinhnong2206 actually he intentionally don't share the script files. The TLDR of why is that he want to encourage us, viewers, to explore the code by ourselves, looking what he did, understanding it and making our own version

@@Pedro_Marangon so I won't be able to figure out what to change so this works with the basic input system than great

ahahaha I totally agree! :P

Ideed, coz I've never seen this style of coding before, and I don't understand it. I can get the logic, mainly because of his explanation, but I still don't understand it.

I don't get it, he should mention about a thing the person don't know to that person go search about it? I think that's too much :P The point of the video is not explain Action or anything else he uses to build the Debug Cheat Console Like Tiago I didn't know what was Action and searched independently Try here, Tiago: docs.microsoft.com/pt-br/dotnet/api/system.action-1?view=netcore-3.1

​@@dnz8792 How exactly does me saying that he should call them by their correct terms so people can do independent research lead to you making the assumption that I said he should explain how they work?

@Steven Docker I totally agree with you, i'm pretty new in the stuff, i understand many things like the new input system, but in this video are missing some parts. its frustrating to me becouse of 2 things, i did not understand how did he trigger the button without listener in the script and the part with private Action command, i understand now the input thing but the Action remembered me of a delegate . And now i'm confused why i need this and where the hell it is implemented.

Thanks you really help me!❤

I was stuck here, thanks man!

thanks

If it weren't thanks to people like you, many of us would be stuck in tutorials like this. Thanks for adding what the tutorial guy thought wasn't relevant.

100% agree. It's similar to MenuCommand and other attributes used by Unity. With some extra work, you could even add documentation to it. Furthermore, you could make it so some methods can have a parameter that takes a list of characters: for console-like command options.

Oh yeah, if someone does this, please add tab auto-completion.

That's a really nice idea, you should really make a tutorial :)

there are a few people that make videos in this format (like Derek Banas) for programmers that just want condensed information. They don't waste literally any time, and the intention is that if something was too fast, you rewind the video. At first this format bothered me for the same reasons it does you; the videos are too fast. After years of dealing with slow, 20 minute videos that explain concepts that could be understood in a tenth that time however, I've come to really appreciate these kinds of videos.

@@LeoninMinecraft Actually yes. I'm going to copy down the process and code I use right below. • Create a folder in "Assets", I usually call it "Input" or some such • in there I go right-click -> create -> InputActions. I do not generate a c# class for it • I pin the Input Actions menu near the scene/game tabs and fill it with the maps/actions/bindings I want. Remember to save it • on the game object I want listening to commands I add the Player Input component, then drag&drop the InputAction asset created before in the first slot, choose the actionmap I want the game object to be obeying, and as for behaviour choose "Invoke unity events". The rest I leave as is. This is all the "prep work" I go through, the rest is done by code using UnityEngine.InputSystem; public class DebugController : MonoBehaviour { private InputActionMap actionMap; private void Awake() { actionMap = GetComponent().actions.FindActionMap("Debug"); // "Debug" is the actionmap name actionMap.actions[0].performed += OnToggleConsole; // I only activate the toggle console trigger at first // it's not optimal, but I grab the actions from the actions array in the actionmap. VERY dependent on the order BuildCommandList(); //builds the list of commands for debugging - not a part of the input system/actions/etc circus } public void OnToggleConsole(InputAction.CallbackContext ctx) { if (showConsole) { actionMap.actions[1].performed -= OnCommandConfirmed; //IF I want to close the console, I deactivate the trigger to confirm commands showConsole = false; return; } else { actionMap.actions[1].performed += OnCommandConfirmed; //IF i want to open the console, I activate the trigger to confirm commands showConsole = true; return; } } } This is the code I arrived to after much cursing and sweat, and it seems to work for me. If you still have problems, do tell and we'll find some solution I hope. P.S. Technically you should also unsubscribe to actionMap.actions[0].performed when the object you are using is to be destroyed. This way you don't run the risk of triggering some left over code from the trash and crashing the program

@@tobiacancelliere6972 Thank you so much my friend!

@@tobiacancelliere6972 Hi thanks for sharing your code, What's OnCommandConfirmed ?

@@telli5868 OnCommandConfirmed is a function that is called whenever actionMap.actions[1] is triggered. As this is for a cheat code inserter, I mapped actions[1] to the "enter" key being pressed, as you would at the end of a command input, so that's when the OnCommandConfirmed method is called. The function itself is merely a string parser to recognise the command on input and looks kinda like this (I don't have the code, new pc): public void OnCommandConfirmed(InputAction.CallbackContext ctx) { if( input == commands[1]) Commands[1](); else if (....) .... } Hopefully it's clear enough?

@@tobiacancelliere6972 Ohh yes thanks !

I actually used something like this for commands of a cli app. It'll be real flexible but yea, reflection with take quite a bit of performance for loading, tho i think it's worth it.

Hey, I know this is a very old comment but I'm trying to implement this as well but I've never used reflection before. I made the attribute and got all the methods with that attribute, I just don't know how to create DebugCommands from those methods, like how to create the generic objects and use the already existing implementation of the method in the action

Personal preference around readability. Habits formed after working on teams with shared code over the years. Making a private variable, and a public getter is much clearer and faster to parse on large projects in my experience.

InputSystem supports different types of joysticks and gamepads. So sometimes you may need a particular value of for example an x axis of the left stick of PS4 controller when callback happens. That's the situation when the InputValue makes sense

Well, whenever you type a new character in the input (check the length of the input string) search your list of commands if they contain the entered letters (command.Contains(input)) and then just display the list of fitting commands on-screen. Then if you click on an entry from that list just execute the regarding command. You can of course advance this with more functionality if you want, but that should work pretty well as foundation.

Currently having the same problem...

put "using System;" at the top of the script

Would you mind sharing this? I'm having trouble with the OnSubmit aspect. It doesn't seem to pass that key to the Input.

Oh nevermind, I found a comment by Mohammed Omar kzfaq.info/love/fSzQ3JjiwmuL0SWMH1uA7Q about how to do it. From them: "An easy fix for this is to add these lines at the end of the OnGUI function and remove them from the update if (Event.current.type == EventType.KeyDown && Event.current.character == ' ') { HandleInput(); input = ""; } "

This isn't an issue at all. That's because I assume that you are using the old input system where the input not associated with global events like the new input system An easy fix for this is to add these lines at the end of the OnGUI function and remove them from the update if (Event.current.type == EventType.KeyDown && Event.current.character == ' ') { HandleInput(); input = ""; }

Hi, i've found it but i can't find where do i bind the key to open it ?