Is there a way to make the CPU just DI and randomly tech (like the beta 4.0 builds) and not attack you?
From my experience putting the cpu into STAY (Debug Menu->General Codes->VS Melee Player Flags->select player 2 on the top->change cpu ai type to stay) both has random DI and the configured tech patterns, while being completely docile and inactive otherwise (though it will recover if you knock it off stage, as it does in training mode).
I tested if it was random by falcon punching a STAY fox cpu and watching the di input via debug mode and it seems random and unpredictable. That said, if you notice it isn't random somehow, please post about it, as my sample size was pretty low, and I don't have the ability to break down the di/tech code to see if it's affected by cpu ai type changes, definitively.
However both your post and (the first part of) this post:
is there an option to revert CPU behavior back to how it was pre-4.05?
seem to be asking a duplicate of:
For the next patch, It would be nice to set the CPU AI for level 1 before it was modified with the new update so that we may be able to practice chaingrabs/tech chases much more easily. If there is a way to do this currently without them attacking me all the time, please let me know!
Which achilles answered here:
Debug Menu --> General Codes --> Player Flags --> and set the player's AI type to something other than normal.
and has been requested and answered a few times since. Please (this is more a psa for everyone and not just you guys) at least skim through a few pages of the thread (at least after the 4.05 release post) before posting questions like these since this has come up and has been answered more than once. Nothing is inherently wrong with asking about it without looking, it just displaces other discussions of bugs and features (as well as the answers of what you're looking for) and does yourself a disservice.
---
Let me know if I shouldn't post this here but I found a small bug in v. 4.05--in the character select screen, when switching from a palette swapped (with L button) Peach (the original color to white iirc) and then moving and clicking to play yoshi instead, but then deciding to switch back to peach, and deciding to switch colors, as I tried to change colors with x and y, it changed from the peach image in the selected character rectangle at the bottom, to yoshi! And I couldn't figure out how to get it back to normal, so, in fear of it saving the game that way (i lack knowledge of how that all works tbh), I exited out via closing the window of the game. Reloading it, it was back to normal. Unfortunately I can't remember if I palette swapped yoshi or even switched his regular colors, I can't remember but again iirc, i didn't switch with the L button and maybe with x and y.
This can also happen if you change Peach to Female Wireframe then hit X or Y a few times, and has extremely similar behavior to the stock glitch which people have linked before in the thread.
---
Achilles if you're reading this the issue I mentioned about being able to cycle through an endless field of azure yoshis on z-alternate characters (except for sheik) still exists as implied by the previous answer
---
would edit but want to add just in case it isn't seen: another bug, the fox lvl 9 AI randomly (well not randomly but i didn't catch the reason it started unfortunately) started doing a full hop to up b diagnoally to the left and koing himself. It was on the hyrule maze level, and i was playing falco, and idk how it happened.
The Fox and Falco CPUs both seem to kill themselves by firefox/firebird-ing off the stage as high as they can, to the left. Other characters jump or airdodge underneath the stage or attempt to recover towards invisible things which do not exist.
EDIT: this applies for the Hyrule Maze levels and is new to 4.05 as it did not happen in 4 beta 4
---
you could acquire an earlier ISO? idk though besides that
Check this out,
http://smashboards.com/threads/the-20xx-melee-training-hack-pack-v4-05-update-3-17-16.351221/
quoting from it, "Note: In-game CPU toggles have not been added back to version 4.0 yet."
I realize you're trying to help, which I relate to and appreciate, but you're being incredibly misleading, as far more constructive answers to this exact same question been provided a few times previously in this thread, which neither you nor the person you're answering seem to have read. Also, your second link refers to in-game cpu toggles via L/R and the dpad (a feature of 3.02 based upon vanilla debug mode's debug information toggles) which is different than what was being asked.
---