Opened 4 years ago
Closed 3 years ago
#11759 closed defect (fixed)
MADS: release build 2.2.0 can run unfinished game
| Reported by: | fedor4ever | Owned by: | bluegr |
|---|---|---|---|
| Priority: | normal | Component: | Engine: MADS |
| Version: | Keywords: | ||
| Cc: | Game: |
Description
game ID 'dragonsphere'
Lol. I propose isolate in source level unfinished games. In module.mk move code to scope UNFINISHED_OBJS. And concatenate them if RELEASE_BUILD not set.
Os: windows, symbian.
Change History (5)
comment:1 by , 4 years ago
| Owner: | set to |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
comment:2 by , 4 years ago
| Resolution: | invalid |
|---|---|
| Status: | closed → new |
Is it normal to run unfinished games in release?
comment:3 by , 4 years ago
| Summary: | release build 2.2.0 can run unfinished game. → MADS: release build 2.2.0 can run unfinished game |
|---|
@fedor4ever
If the game in question shares a lot of the underlying engine code of an already supported game (Rex Nebula, in this case) it would be pretty useless (and a waste if time and resources) to add code which explicitly forbids the "yet not fully supported" game than to work towards supporting it completely.
Just look at the Wintermute engine/games.
comment:4 by , 4 years ago
May help simple exclude detection code in release build. It's good to exclude dragonsphere folder in module.mk from release build.
comment:5 by , 3 years ago
| Owner: | changed from to |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Fixed by adding a subengine for V2 MADS games in c6b164a0aa75ae18aa42a639c5591bef4cf316ec
You are not reading the messages. The game has clearly set ADGF_UNSTABLE flag. The users will be warned that the game is not supported unless they deliberately suppressed that warning.
Lol on you.