google-code-export / assaultcuber

Automatically exported from code.google.com/p/assaultcuber
0 stars 0 forks source link

3D checks for secure flags #156

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What new or enhanced feature are you proposing?

Capture flag for
stay close to the flag.

I mean that add vertical identification to capture flag.

Example map under, where you see problem with current system.

What goal would this enhancement help you achieve?

Get better secure flag.

Original issue reported on code.google.com by rh.nkr...@gmail.com on 19 Jan 2014 at 3:10

Attachments:

GoogleCodeExporter commented 9 years ago
At first I could not interpret it, but I see what you mean now.

You mean that there should be a vertical height offset for flag entities.

The engine is currently using attr1 for type, attr2 for team, attr3 for enemy, and attr4 for progress.

I guess attr3 could handle both team and enemy and attr4 could still be used for progress, leaving attr2 for the offset.

However, I cannot see how this is problematic in the map you provided.


I now realize what you mean: the secure flags should have 3D instead of 2D 
checks.

Original comment by theonlypwner on 21 Jan 2014 at 12:20

GoogleCodeExporter commented 9 years ago
Fixed and verified in 2a18c9a19c48559a6841addd4cb54ab7a858edac

Original comment by theonlypwner on 21 Jan 2014 at 12:39