Kronzky – User talk
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
:But then, why is player ''not'' null if he's there during the briefing already? | :But then, why is player ''not'' null if he's there during the briefing already? | ||
:And even ''if'' player was null in those particular cases, then I would consider ''that'' to be a bug. After all, it would make the use of init.sqs for player initialization useless... --[[User:Kronzky|Kronzky]] 17:45, 13 January 2007 (CET) | :And even ''if'' player was null in those particular cases, then I would consider ''that'' to be a bug. After all, it would make the use of init.sqs for player initialization useless... --[[User:Kronzky|Kronzky]] 17:45, 13 January 2007 (CET) | ||
::Agreed, but it seems it's only null in JIP. :) I solved it with an '@!isNull player' as player gets assigned after a short delay, but it would be good if it was really fixed (or documented). --[[User:Salisan|Salisan]] 21:07, 13 January 2007 (CET) | |||
Revision as of 21:07, 13 January 2007
JIP and init.sqs
I think you're seeing this because 'player' is null when init.sq(s|f) is run as a player JIPs, it's very confusing.. --Salisan 12:21, 13 January 2007 (CET)
- But then, why is player not null if he's there during the briefing already?
- And even if player was null in those particular cases, then I would consider that to be a bug. After all, it would make the use of init.sqs for player initialization useless... --Kronzky 17:45, 13 January 2007 (CET)
- Agreed, but it seems it's only null in JIP. :) I solved it with an '@!isNull player' as player gets assigned after a short delay, but it would be good if it was really fixed (or documented). --Salisan 21:07, 13 January 2007 (CET)