okopanja Posted July 11, 2022 Posted July 11, 2022 (edited) DRAFT: brainstorming in progress This feature would function like this: - with every kill a kill mark gets added to the airframe - the marks would be tracked at server level (so no mixing between different servers) - once the player gets killed his/her next airframe has no kill marks. Edited July 13, 2022 by okopanja DRAFT
upyr1 Posted July 11, 2022 Posted July 11, 2022 I'd rather track it at the player's level so those of us who play mostly off line get the kill marks too 1
okopanja Posted July 11, 2022 Author Posted July 11, 2022 (edited) I accidently clicked on report. Applologies both to you and stuff member. 37 minutes ago, upyr1 said: I'd rather track it at the player's level so those of us who play mostly off line get the kill marks too That could be an additional variant which does not conflict the per server marks. Painted would be made only on RTB and succesful landing. Edited July 11, 2022 by okopanja
Dragon1-1 Posted July 11, 2022 Posted July 11, 2022 (edited) They should be tracked per server and per aircraft type, IMO. Anything can happen in SP, and it's only fair that those who want kill marks in MP earn them the honest way, so no cheating with an SP mission or a self-hosted server filled with novice AIs. In SP, they should be tracked per campaign, maybe with an option for a campaign to look at another campaign's data, if present, and add kill marks from that one (in case of multiple campaigns featuring the same main character). Ideally, there would be an option to somehow keep track of AI wingmate kills, and use that to set kill marks for when that specific teammate shows up in another mission. It would add a lot of immersion. For non-character driven campaigns (could also be an option for servers that don't care), there could be an option to use player's actual kills in that particular airframe, but that'd require some Rogue Squadron-style trick like painting a red mark for every squadron killed, because a long time player can possibly rack up hundreds of AA kills. Another nice idea is a customizable style for marks, since different pilots painted different things for their kills. Some indicated nationality (particularly in WWII), some put in a silhouette of their kill (US pilots seem to like that one), and some would just paint a dot or a bar. Edited July 11, 2022 by Dragon1-1
upyr1 Posted July 13, 2022 Posted July 13, 2022 On 7/11/2022 at 11:57 AM, Dragon1-1 said: They should be tracked per server and per aircraft type, IMO. Anything can happen in SP, and it's only fair that those who want kill marks in MP earn them the honest way, so no cheating with an SP mission or a self-hosted server filled with novice AIs. In SP, they should be tracked per campaign, maybe with an option for a campaign to look at another campaign's data, if present, and add kill marks from that one (in case of multiple campaigns featuring the same main character). Ideally, there would be an option to somehow keep track of AI wingmate kills, and use that to set kill marks for when that specific teammate shows up in another mission. It would add a lot of immersion. For non-character driven campaigns (could also be an option for servers that don't care), there could be an option to use player's actual kills in that particular airframe, but that'd require some Rogue Squadron-style trick like painting a red mark for every squadron killed, because a long time player can possibly rack up hundreds of AA kills. Another nice idea is a customizable style for marks, since different pilots painted different things for their kills. Some indicated nationality (particularly in WWII), some put in a silhouette of their kill (US pilots seem to like that one), and some would just paint a dot or a bar. How about options?
Dragon1-1 Posted July 13, 2022 Posted July 13, 2022 As I said, per server and aircraft, or per player and aircraft, so there you have your options. Too many choices are a debugging nightmare, since the number of possible combinations rises exponentially.
okopanja Posted July 13, 2022 Author Posted July 13, 2022 I gather this should be sort of a crowdsourced feature wishlist, so I marked it as DRAFT
Recommended Posts