Hi there, I have a kind of odd question. In proffie, is it possible to have the PWR button turn on the blade of a saber, but then the AUX button turn it off? My current understanding is that this can’t be done, but my understanding of what I’m doing is literally at the level of a cargo cult. Is this possible if I were to, for instance, go messing about in the prop file?
Of course it is possible, if you know your way around C/C++ code. But you need to make sure that nothing else gets “affected” by the change:
- what is the power button doing while saber is on
- are you in battle mode or not in battle mode
- what happens to the code/button when you are in a “menu”
- …
If you plan on changing a simple(ish) prop it can be fairly easy, but with a complex prop, one change will bring a cascade of other changes that will need to be made or at best you will loose functionality and at worse it will just not compile or work.
Which prop file are you talking about ?
At this point my question is more of a general one than one dealing with a specific saber/prop file/config/etc. As I lack a working knowledge of C or C++, I think it would probably not be something I’d be able to do, in any case.
If you take the simplest prop (fewest functions): saber.h (or maybe even saber_sa22c_buttons.h) it is fairly easy and probably only requiring just a few lines of code to be swapped.
If you take the most complex coded prop (maximum functions crammed in one code): it is probably not possible without a full re-design of the whole button code section, because one button change will bring a multitude of other things that will need to be changed, and those changes will bring more things that will need to be changed, … . Good luck with that one.
With saber.h (it is only 235 lines of code) copy the code section in an AI, ask what does the code do (most of it reads almost like it is English, once you learn a little bit how to “decode” the C/C++ code), tell AI what you want. AI will probably tell you to swap line “abc” with line “xyz”, done. The longer the prop code is, the harder it becomes.
Note: If your AI generated code doesn’t work, do not ever post it here (it is against the rules to post AI generated content on The Crucible)
Ah, well I don’t particularly want to mess about with AI, especially since then I couldn’t come here for help, so I think I’ll just have to leave this at that. Thank you for the information, though! It’s neat that it’s at least theoretically possible.
That’s not quite true. This is what the rules say:
The intent behind this rule is to offer help to people who want to learn. It’s ok to use AI, but it’s not ok to use that an excuse for not learning. People who just want the AI to do it without learning anything can just stick to chatbots.
If anybody has a better way to express this, I’m all ears.
What I meant was: if the code is generated by AI, AND it doesn’t work (verified by a human that it DOESN’T work, or NOT verified that it DOES indeed work), then don’t post it here.
I should say that I understood Olivier’s meaning here; if I had to come here for help with AI-assisted code, it would of course not be working. So the policy is quite intelligible, no fear.
I just wanted to explain, because it’s not my intent to prevent all AI content, neither is it my intend for this rule to get in the way for people actually want to learn.
To put it another way; use your brain.
4 Likes