Currently the capture contexts are instantiated in the sequence builder and only have one instance each per sequence. This is fine, but it suffers from the problem being each sequence may be used by many different players. The issue with this is that the capture context stores the valuation container full of data in the context capture. This means that data between more than one player may get confused between and get updated more than needed. Storing data like this is not the intended result of having one instance per sequence and should be changed immediately to methods that allow you to input a container and a player allowing it to return the container when it has captured it's data. This will work a lot better for the newest capture and sequence refactor.
Currently the capture contexts are instantiated in the sequence builder and only have one instance each per sequence. This is fine, but it suffers from the problem being each sequence may be used by many different players. The issue with this is that the capture context stores the valuation container full of data in the context capture. This means that data between more than one player may get confused between and get updated more than needed. Storing data like this is not the intended result of having one instance per sequence and should be changed immediately to methods that allow you to input a container and a player allowing it to return the container when it has captured it's data. This will work a lot better for the newest capture and sequence refactor.