ArmA Warfare/1.1/Issues – Talk
Jump to navigation
Jump to search
mNo edit summary |
|||
| Line 1: | Line 1: | ||
=Wishes= | |||
==Switching sides will result in screen blanking== | ==Switching sides will result in screen blanking== | ||
[http://www.flashpoint1985.com/cgi-bin/ikonboard311/ikonboard.cgi?act=ST;f=81;t=74191 | [http://www.flashpoint1985.com/cgi-bin/ikonboard311/ikonboard.cgi?act=ST;f=81;t=74191 BI forum thread] | ||
<<[[ArmA_Warfare/1.1/Issues#Wishes|Article]]<br> | <<[[ArmA_Warfare/1.1/Issues#Wishes|Article]]<br> | ||
The bugs section of this page is being drowned out by the wishes section and with the page being called issues... What about moving all of the wishes to a dedicated Warfare wish list page? --[[User:MSG Trit|MSG Trit]] 02:10, 25 June 2008 (CEST) | The bugs section of this page is being drowned out by the wishes section and with the page being called issues... What about moving all of the wishes to a dedicated Warfare wish list page? --[[User:MSG Trit|MSG Trit]] 02:10, 25 June 2008 (CEST) | ||
Revision as of 13:31, 23 July 2008
Wishes
Switching sides will result in screen blanking
<<Article
The bugs section of this page is being drowned out by the wishes section and with the page being called issues... What about moving all of the wishes to a dedicated Warfare wish list page? --MSG Trit 02:10, 25 June 2008 (CEST)
- I've chosen the word "issue" but not being an english native it's maybe the wrong one. As I know, in IT it's used for both bugs and request feature, as briefly described here.
About the wishes being more than bugs, you are right. I suppose there are more bugs than described here. However, I'll prefer to have dedicate pages for each dev chosen wishes/bugs with design and/or implementation details. In the meantime, keeping whishes and bugs together should help to see if an issue is a bug (it should work as documentation/help says, but it doesn't) or a wish (should work like I want, but it doesn't). alef 11:45, 25 June 2008 (CEST)
Bugs
Non player controlled AI in AA pods
<<Article | BI forum post>>
AI in pods should
- be in "Open fire" engage rule (or "Engage at will"?)
_u setCombatMode "YELLOW" (or "RED"?)
- be combat mode "Danger"
_u setBehaviour "COMBAT"
- doing a "Scan horizon"
- No simply "scan horizon" command has been found in BI/OFPEC forums. Maybe need an implementation. Or, more simply, a server trigger.
Server AI get in as gunner at Common\Functions\Common_UseStationaryDefense.sqf, line 32.
alef 17:51, 25 June 2008 (CEST)