-
Notifications
You must be signed in to change notification settings - Fork 657
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
Factorio: update API use #3760
Factorio: update API use #3760
Conversation
Thank you 🎉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes LGTM. Generations are completely different, presumably because of the random changes, but the playthrough seems similar (I don't know the game really at all though, just going off of item names). A few minor comments.
Co-authored-by: Exempt-Medic <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Random generations didn't hit any old options stuff and I didn't find any with a search. Generations before and after are consistent if the random
changes are reverted. Comments were fully addressed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pure code review; did not run gens/tests/etc., did not check for completeness
updates all looks fine, got a little worried about changing the 'world' parameter in technology.get_custom() to the World instance instead of MultiWorld, but digging through that codepath it seems to be fine/correct
# Conflicts: # worlds/factorio/__init__.py
What is this fixing or adding?
updates various Factorio API use to current AP standards.
How was this tested?
unittests and a single local gen