Review - Split the mission class
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Humanity Project |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Copying from the email reviews to make it easier to follow up on code reviews. I'll create a few bugs on the same principle. This one is targeted for the next version.
the Missions class needs to be split between a Mission class
(that is subclassed by the actual missions classes, such as
FirstMission) and a MissionEngine class, that is responsible for
instantiating mission objects, saving/restoring them (methods such as
save_state()) or calling the right method corresponding to an action
(process_
=> this will allow to only expose methods in Mission that can actually
be needed by someone scripting a mission, not the underlying magic. It
also gives more flexibility, allowing a player to run several missions
at the same time for example
Changed in hackit: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Vlad Dragu (vlad-dragu) |
milestone: | none → alpha3.0 |
Changed in hackit: | |
assignee: | Vlad Dragu (vlad-dragu) → nobody |
milestone: | alpha3.0 → none |
Changed in hackit: | |
status: | Confirmed → Fix Released |
milestone: | none → alpha3.0 |