...
I should also explain that what Zlomus mentions as ObjectCounter is in fact level config pointer. Object counter is a different thing that only corrupts attibutes like the stick in level 4, most of the time it only corrupts sprites.
...
I thought that mechanism what's creating objects and make counts which slot should be used to spawn object it was called ObjectCounter (that's probably my misinterpretation - nevermind). Thanks for correcting this (probably it should be called correctly level object counter) for me is really important information.
feos wrote:
...
Regarding legality.
If you can make the PC jump to arbitrary locations, that should be used in any% if it makes it faster, possibly in a playaround too, but it's banned from other branches, because there ACE would be considered sub-optimal and arbitrarily limited. If you don't use techniques that allow PC to jump to arbitrary locations, then you can corrupt memory all you want in non-any% branches.
Summarizing all of this.
In non-any% branches (whatever this means) I could use glitch but this glitch has to be controlled, because some objects can corrupt pc pointers which is illegal in this case, isn't it?
...
Does anyone have any ideas for strategies I could try going forwards to put this all together into a working strategy?
I have an idea! If you'll look inside Zlomus pack there is a lua script that could be very useful in this case. Only one thing you have to do is a change the searchMemory to true. Then you'll be able to see all possible cases where the warp could be spawned (this maybe useful to find other strategies too).
But what's about adding new rule to your run and do it in Zlomus way? This would be legal too in the meaning of TAS law, because we just added new rule and done it in this way for example:
We declare that our run must comply all of this rules:
*Our run can use warp portals,
*Our run can use game glitches,
*Our run cannot game end until it reach Armageddon level and Dark Queen wasn't beaten in battle.
These 3 conditions were met in this run, because there is no game end glitch here. Extra fourth rule which could be "Any illegal pc instructions and executions are acceptable in the meaning of our target" (as I introduced before), is givin' to us information what kind a glitches we could use to make our run following the rules.
What do you think about this?
Hi there! I'm new here so please (if you don't mind), I want you to approach to all of my content in a friendlier manner (just in case of any hater).
First thing first, I wanna regard to Lobsterzelda question which is:
Lobsterzelda wrote:
...
Should the current Battletoads 2P Warps TAS be allowed to execute a jump to the warp portal code in memory?
...
I know that I don't have a right to this but for me is acceptable with a condition which is:
Any illegal pc instructions and executions are acceptable in the meaning of our target (which is a warp to level 5 in this case)
This is probably debatable because is using "deep glitch" to reach our destination and you are forced to create new some kind division of glitches? (ain't that right?)
In other hand we have a sample where is existence of overflowing object counter pointer (as Zlomus underline it in his notes, it is a possibility). This point of view should be fully legal in the meaning of TAS law.
Version with double level warp is pretty exiting, because is useless to any of TAS-es (I guess there is no classification for that TAS -> and never 'll be).
This PJ Glitch (as Zlomus callin' it) is a part of big deal that probably I'll never understand but it's really exiting to hear that (btw what's about the movie, any suggestions?).
And the last thing, do you have any questions about all of this?
Best regards from me to you dudes!