feat: stateless engine shutdown #15

New issue

Open

opened 2024-11-24 12:57:49 +01:00 by JeremyStarTM · 0 comments

JeremyStarTM commented

2024-11-24 12:57:49 +01:00

Owner

Feature description

Having the engine be fully stateless after shutdown and allowing it to start up again would be a major benefit. This would not only benefit our testing setup, removing the need to run multiple JVMs in parallel, but would also allow developers using our engine to fully restart the engine without restarting the JVM, which may be required in certain scenarios.

Feature implementation

Code will be required for all variables to be reset to their original values. Everything needs to be cleaned up. Additionally, we may need to check if any engine-provided resources are still accessible to the application or game. Accessing them while the engine is uninitialized may cause major issues.

Feature alternatives

No response

### Feature description Having the engine be fully stateless after shutdown and allowing it to start up again would be a major benefit. This would not only benefit our testing setup, removing the need to run multiple JVMs in parallel, but would also allow developers using our engine to fully restart the engine without restarting the JVM, which may be required in certain scenarios. ### Feature implementation Code will be required for all variables to be reset to their original values. Everything needs to be cleaned up. Additionally, we may need to check if any engine-provided resources are still accessible to the application or game. Accessing them while the engine is uninitialized may cause major issues. ### Feature alternatives _No response_

JeremyStarTM added the

FeatureRequest

New

label 2024-11-24 12:57:49 +01:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference: StarOpenSource/Engine#15

No description provided.