Experienced Forum User, Published Author, Experienced player
(855)
Joined: 4/27/2018
Posts: 66
Ok let me rephrase:
Any kind of fights or less than civil conversations anyone has had with Spike are not relevant here. This thread is about discussing the TVC flooding not to discuss his so called "toxicity".
And by "valuable" I'm pretty sure they mean his publishing work. Which again is not related to him being a dick. (Sorry Spike.)
Maybe stop discussing unrelated stuff and nobody would have to till you to stay on topic.
And I never said anything about relation to the first post because it has parts of the other incident because of the thread split.
Experienced Forum User, Published Author, Experienced player
(855)
Joined: 4/27/2018
Posts: 66
For like the fifth time this thread isn't titled "Reasons I hate Spikestuff"
Him dicking around here isn't in any way related to the flooding incident.
It in no way implies that he's the only one that would've done it if he was mad. Anyone could've under the right circumstances. Stop using it as a way to take him down for the wrong reason.
Experienced Forum User, Published Author, Experienced player
(855)
Joined: 4/27/2018
Posts: 66
Nach wrote:
On the bright side, it also led us to looking into making certain improvements in the site itself to prevent even unintended related issues in the future, and that's a great thing.
This should include the following:
When someone tries to help the site (for example, with encoding), it's completely natural for them to mess up at first. Instead of other encoders fixing it by themselves and saying that X has messed up, it's better if they tell the person what they did wrong and kindly asking them to fix it, and possibly help him with that. That's how people learn. Not by being told they messed up. Which includes comments on YouTube.
Not to stir the pot again and I'm aware that Ezgames and Fsvgm are good now, but what happened concerns me that if someone would want to help this site in the future, seeing what happened here is gonna make them reconsider that. Especially coming from senior staff.
Experienced Forum User, Published Author, Experienced player
(855)
Joined: 4/27/2018
Posts: 66
EZGames69 wrote:
I would really appreciate it if a statement was made IN LIGHT of the new information, not old threads prior to this new information.
So Spike has already apologized and this:
I've spoke to all involved at the time. They gave me their word that they will not perform any activities which look like publication burying in the future. As these are private discussions, they will not be quoted.
Happened. And you're still looking for statements? Funny you actually quoted the very first part of this statement which is recent in your other post.
Are you really focusing on the issue or is this turning into "I have personal issues with Spike I would like to see him punished" ?
Experienced Forum User, Published Author, Experienced player
(855)
Joined: 4/27/2018
Posts: 66
What a mess.
In my opinion, as much as Spikestuff is kind of rude and has an opinion on everything (that's a compliment) , I don't think he would do something like that. I agree there are a lot of connections between him and the other accounts, but why would he tweet about it? If he has done anything like that he wouldn't try to get the attention these tweets do.
Another thing worth noting is the language used in most of these comments is a bit more cruel than Spikestuff's.
-
I'm not defending anybody nor I am pointing fingers, but it's just what I noticed.
Experienced Forum User, Published Author, Experienced player
(855)
Joined: 4/27/2018
Posts: 66
feos wrote:
The only question would be, are there any exceptions? From reading the above, I'm not exactly sure if "There's no other way to traverse that area without the corner bug anyway" refers to a voluntary exception or to simply having no way to avoid the glitch.
That's a poor choice of words on my end, I apologize.
Like Memory said:
Memory wrote:
Point was there is that the intended way (the trampolines) was the only method of traversing that area ASIDE from the corner bug.
You can either use the jump pads to go through that area as intended (not 100% what they intended though, the use of the second jump pad skips a small area, but no glitches were abused in doing it so..)
or you can use the corner bug (or a variation of it using the jump pads themselves) for glitched runs, like this:
Corner bug: https://youtu.be/M-jSw1PhaP0?t=2683
variation(informally named the jump pad bug): https://youtu.be/9sxl6TPepWU?t=9
this movie uses the jump pads to shoot the bells to open 3 doors, because it's the only way to traverse the area without the use of these glitches (or any other).
Experienced Forum User, Published Author, Experienced player
(855)
Joined: 4/27/2018
Posts: 66
Memory wrote:
Personally I don't quite understand the nominations for me either, given that the guidelines for this award are based on publications. I feel I didn't put that much out there this year compared to a bunch of the other candidates, I tended to be busy with other stuff.
My nomination happened because after watching your work I could feel everything was both perfect and entertaining.
Experienced Forum User, Published Author, Experienced player
(855)
Joined: 4/27/2018
Posts: 66
Memory wrote:
A technicality that I forgot to mention is that enemies will go through blocks while you're pushing them and that happens in this TAS. One could probably see this as a glitch though it's not particularly helpful to the player.
The block pushing/pulling mechanics are a bit weird. Both Lara and the block she's pushing actually move at the last frame of the push/pull animation. So during the pushing/pulling enemies would attack the initial position of Lara when she started pushing/pulling, as seen in The Great Wall, the first level in this movie. And the solidity of the object would still be in the position before it "started moving", so enemies/not enemies might walk through the moving object because to the game the block hasn't actually moved yet.
Now Barkhang Monks are a bit special. Their pathfinder can sometimes completely ignore the boxes even if they aren't moved etc.. not too sure if it's a bug or "intended behaviour" (in this case the developers probably just forgot though), but it's not something caused by anything the player can control. It "just happens". And as Memory said it doesn't serve much help to the player, it just looks weird.
The main unifying thing behind the glitches that are not used is that they more or less change how the game is played. You can very much skip large portions of levels using these various glitches.
Indeed, but that definitely isn't measure for "what is a glitch" either. Ofcourse some glitches also save up to the minimal of a couple of frames without skipping much of the level, and a normal jump-grab can skip quite a bit of gameplay. Also, from what I understand glitches in Tomb Raider aren't defined on a case by case basis because of the way the game is made, instead it is generalised that doing X (for example clipping in geometry) is considered a glitch, doesn't matter if it saves one or two frames or 3 seconds, or if it even loses time, a glitch is a glitch. Same thing applies to normal manoeuvres, just because a normal jump may skip a big part of a level wouldn't mean it's considered a glitch to jump there.
Experienced Forum User, Published Author, Experienced player
(855)
Joined: 4/27/2018
Posts: 66
I would say it pretty much comes down to what the Tomb Runner community have decided over the years, and what follows the basic principles of the manoeuvres Lara is capable of doing.
But to try and explain:
Respect the solidity of objects and terrain (cutting corners is ok though)
This one is pretty self explanatory, clipping into geometry is not allowed. Most of the time it causes Lara's Y coordinate value to go haywire and so pushes her on top of the structure she's clipping into. Now when it comes to geometry, there is "strong" and "weak" geometry. Strong geometry is walls that Lara can't clip into normally. Weak geometry is the type Lara can just go through, such as corners. -A mismatch in the collision detection causes her to clip in the strong collision area-. Going deep enough into a corner but not enough to reach the strong collision allows Lara to completely skip the tile next to the corner, that's considered deep enough as a clip.
Objects are a little different, there are two types of objects. "Hard" and "soft" objects. Hard objects such as fences completely stop Lara from moving. Going through them is considered a glitch. Usually the game will do it's best to keep you from clipping into a hard object, it would even clip you into a wall if there's one right next to the object. Soft objects are ones that don't stop Lara completely, instead she collides with them in a way so they can push her around, such as doors and enemies. These can be clipped through by doing continuous running jumps into the object, which is not allowed. (Most doors can't be jumped through due to the game's portal engine but that's irrelevant)
Nothing that drastically changes where Lara is height-wise in the level
This points to the bug mentioned above^. Note that in Tomb Raider 2 the level Ice Palace has some jump pads that push Lara up quite some distance, those are obviously fine and are used in this movie. (There's no other way to traverse that area without the corner bug anyway)
Items are to be used as intended, no duplication
I believe this refers to the "dupe glitch", used in the Barkhang Monastery level in glitched runs. This bug is the result of the severe hardcoding the ring inventory, as the inventory code contains item names (yes). This bug abuses different names in similar slots. A workaround of this bug does exist in the code, but is buggy itself and is completely ignored if you go through the inventory manually. Here is a video of this bug in action: https://youtu.be/go_J7zCmNiY
No sorts of save/reload related glitches (these can have various effects)
These types of glitches happen because a particular function to save certain values into save files fails to execute and is completely ignored, so the save ends up without them, and when reloading that save the value would be either missing or 0.
Experienced Forum User, Published Author, Experienced player
(855)
Joined: 4/27/2018
Posts: 66
You basically have to avoid anything caused by programming errors in the game itself.
Now it might be hard to decide if a certain trick is a glitch or not especially without knowing what happens in the background. For example, flare cancels. They indeed don't look that glitchless, but in reality it's caused by an animation setting the developers did, without thinking it could cause certain animations to be skipped. Stumbles can also be cancelled by simply pressing roll when you fall, she rolls as soon as she lands, for the same reason flare cancels work.
-ofcourse "looks glitchy" isn't a factor-
Experienced Forum User, Published Author, Experienced player
(855)
Joined: 4/27/2018
Posts: 66
Thank you EZGames !
Memory wrote:
The snowmobile section was great.
Now, it seems there does not appear to be a written definition for glitchless, not even in the RTA community's leaderboards. It would be appreciated if the kinds of glitches avoided were listed somewhere.
I'm thinking what's a better way to compare than viewing an actual run
https://www.youtube.com/playlist?list=PLJrh64hniuh1r2nUG91CiGoZoLx69U2IX this is Bahamete's glitched WIP.
-
I haven't really considered writing something like that up but I can point out glitches that save time the most.
