elementhttp Posted November 23, 2019 Posted November 23, 2019 Hi there ! Long time no see This is the current pipeline: edit code in function-> compile code -> run the game -> load a save -> test modification So you can see the problem now . Any small changes to the code requires long time to test . Question is how to reduce the pipeline size (or reduce modded changes testing time ) ? Some hypothetical examples: eg1. run the game-> load a save (or map) -> edit code in function during program execution -> test modification eg2. run the game and load map in single command -> edit code in function during program execution -> test modification Smoo likes this
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now