-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Normal difficulty - Requirements issues with SJ, Boost, Spider, Charge/Supers, bombs #1
Comments
Fiery Shores Morph Ball Track also has the opportunity of BEING the Morph Ball, and only requirements listed for normal are Suit and Missiles. If this is the only way to get it: https://www.youtube.com/watch?v=-th9aXgr-dM then, in my opinion, it should not be a "normal" difficulty. Maybe I'm just terrible at scan dashing, which, for the record, I am and I know it lol... But usually, I can do most tricks though after several attempts, (I've done the Grand Abyss dash in MP2 on a few occasions) and I couldn't hit this one for the life of me... I can do most where there is a little bit of error allowed, but this one seems like it is slightly too precise of a trick to be considered a "Normal" trick. Again, if there's another method of getting it (without space jump), I am ignorant to it, so then this can be ignored! I'd also like to know what it is! ;-) |
hey! half a year later but I've taken it upon myself to try to nail down some of these spikes in difficulty, but I'm having a bit of trouble turning my changes into an executable I can test, so if either of you are savvy with that I would be very thankful for your help with that and with finding a new ground for Normal Difficulty. |
Hey, sorry I've been inactive on this. I've just been busy with school. What part of the build process are you having difficulties with? |
I'll start by saying I'm totally out of my element when it comes to github and projects as a whole, haha. I've tried a bunch of different things to try to get the Makefile (searches led me to visual studios, mingw, and cygwin) to behave but everything seems to get caught up on main.o and I'm not savvy enough to figure out why. All I know is that my change to logChecker.cpp passed a syntax inspection. |
That's probably the c++ compiler tripping up on the threading. It requires a compiler with posix threading and most windows c++ compilers have win32 threading. If you want, I can build it for you if you give me your logChecker.cpp file. |
if it's not too much trouble, that's exactly what I've been hoping the past few days! this one is up-to-date https://github.com/WashedUpLinkshot/new-prime-seed-generator/blob/master/src/logChecker.cpp and if you want to review the changes, I've got the comparison here master...WashedUpLinkshot:master |
Here you go: Thanks for your input. I'll take a look at your changes. |
During a bingo race this past weekend, we used seed 1522623418 with no exceptions, and had quite a randomizer to play with. Log file has been attached, but the most interesting item placements were as follows:
Our bingo card, for reference, had "obtain all 3 Frigate items" as well as "Flamethrower", which coincidentally was in Biohazard containment this seed. Both goals were not completeable because of Charge Beam's unobtainable location.
I have also obtained a seed with bombs in Ruined Shrine upper ledge, and space jump at Early Wild, requiring the Ruined Shrine 21% dash strat to complete.
Lastly, it is possible for Super Missiles and Spider Ball to appear in the Phendrana Shorelines spider track location, making them unobtainable inbounds (if they're even obtainable out of bounds at all). While I understand they are luxury items and aren't required for the given seed they are generated in, I'm not sure if there's a good reason for them to be unobtainable for less-experienced runners, unless this was just an oversight with the requirements checking (which is completely understandable).
Let me know if you need any further details. I'll try to dig up the seed I played which had the early wild SJ and Ruined Shrine bombs later.
Prime_Randomizer_Log-2017-08-07_10-56-51-AM.txt
The text was updated successfully, but these errors were encountered: