| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0005246 | Spring engine | Lua | public | 2016-05-18 16:50 | 2017-06-01 20:01 | ||||||||
| Reporter | Google_Frog | ||||||||||||
| Assigned To | |||||||||||||
| Priority | low | Severity | feature | Reproducibility | N/A | ||||||||
| Status | new | Resolution | open | ||||||||||
| Product Version | 101.0+git | ||||||||||||
| Target Version | Fixed in Version | ||||||||||||
| Summary | 0005246: Feature: Spectator only unitRulesParams | ||||||||||||
| Description | I want an access level of unitRulesParam which cannot be read by any player. My use case is a spectator view which keeps track of what each player has seen. I want to use unitRulesParams to mark which allyTeams have seen a unit but with the current system this would reveal information to the players. | ||||||||||||
| Tags | No tags attached. | ||||||||||||
| Checked infolog.txt for Errors | |||||||||||||
| Attached Files |
| ||||||||||||
Notes |
|
|
hokomoko (developer) 2016-05-18 17:37 |
You can get prevLos by using GetUnitLosState with the raw arg on (Assuming you are a spectator and you have full read) |
|
sprung (reporter) 2017-06-01 18:08 |
How about other use cases? It sounds like a good way to announce pre-generated randomness. Example: a larger unit that on death turns into a random unit of lower cost. Players don't know in advance and have to play around it, but specs do because it makes for fun anticipation. |
|
hokomoko (developer) 2017-06-01 20:01 |
This is basically https://github.com/spring/spring/pull/196 right? |
Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-05-18 16:50 | Google_Frog | New Issue | |
| 2016-05-18 17:37 | hokomoko | Note Added: 0016326 | |
| 2017-06-01 18:08 | sprung | Note Added: 0017761 | |
| 2017-06-01 20:01 | hokomoko | Note Added: 0017763 | |


