GermanyMod Message: Time starts at 5.633 and ends at 1661.800 at 30 fps to get a final time of 0h 27m 36s 167ms. Retimed using yt-frame-timer
Hey, this all sounds very exciting. Tomorrow the university starts again, so unfortunately I won't have time to take a closer look at these things. But with time I'll look at it for sure. Thanks again for sharing :)
Mod Message: Time starts at 9.967 and ends at 7409.533 at 30 fps to get a final time of 2h 03m 19s 567ms. Retimed using yt-frame-timer
Mod Message: Time starts at 9.867 and ends at 1830.100 at 30 fps to get a final time of 0h 30m 20s 233ms. Retimed using yt-frame-timer
Mod Message: Time starts at 9.300 and ends at 2047.733 at 30 fps to get a final time of 0h 33m 58s 433ms. Retimed using yt-frame-timer
Mod Message: Time starts at 9.300 and ends at 2047.733 at 30 fps to get a final time of 0h 33m 58s 433ms. Retimed using yt-frame-timer
Mod Message: Time starts at 6.667 and ends at 1067.200 at 30 fps to get a final time of 0h 17m 40s 533ms. Retimed using yt-frame-timer
Mod Message: Time starts at 6.667 and ends at 1067.200 at 30 fps to get a final time of 0h 17m 40s 533ms. Retimed using yt-frame-timer
Mod Message: Time starts at 8.233 and ends at 1285.433 at 30 fps to get a final time of 0h 21m 17s 200ms. Retimed using yt-frame-timer
Mod Message: Time starts at 10.533 and ends at 382.433 at 30 fps to get a final time of 0h 6m 11s 900ms. Retimed using yt-frame-timer
Mod Message: Time starts at 10.533 and ends at 382.433 at 30 fps to get a final time of 0h 6m 11s 900ms. Retimed using yt-frame-timer
Hey, yes I believe you. It's certainly very cool to know that you can have a big impact on a community and its runs by finding bugs and glitches :) Thanks for sharing them!
let's turn this into a discussion thread.
The bugs currently labeled as glitch can now be found under the Game rules. These glitches are just allowed in Any% runs
that is really very exciting! If you still think of something, then you can post it here :) Thanks a lot for sharing!
Do you have any plans to look further for glitches at some point?
Must see what we label it as a glitch and what not
Hello Geta92,
I understand your objection and it is quite justified.
The categorization of what is a glitch, I have made myself. So this merely represents my opinion.
I am also relatively new to the speedrun scenes. I've been watching for a relatively long time, but I've only been active for a short time, so I don't have much experience yet.
What I could determine in my observation time, however, is that communities to games themselves define what should be considered a glitch and what not. This happens in the course of votes of all interested people of the corresponding community. When such a vote can be representative for Anno 1602 is difficult to assess, since only very few are currently active.
The basic idea was to list the save-load mechanic as a glitch. Otherwise, runs with this bug would not be legitimate in case of a later decision that this is a glitch and one would have to give time penalties or take the run completely out of the rating. This was to be avoided. You can always go the other way without any problems.
For my part, I am of course positive about a survey.
Regarding cheats: So-called "cheat codes", which exist in Anno 1602, are already forbidden by the website with the site rules. So there is no need for an explicit mention here.
Kind regards invi
Mod Message: Time starts at 2.967 and ends at 10.100 at 30 fps to get a final time of 0h 0m 7s 133ms. Retimed using yt-frame-timer
Mod Message: Time starts at 10.233 and ends at 225.033 at 30 fps to get a final time of 0h 3m 34s 800ms. Retimed using yt-frame-timer
Mod Message: Time starts at 10.233 and ends at 225.033 at 30 fps to get a final time of 0h 3m 34s 800ms. Retimed using yt-frame-timer
