Project Reality Forums

hi,

i know this is a suggestion and the suggestion forum is closed for a reason, but as i understood it, it is closed for the reason of people complaining about changes in the new patch ("short" after the release), while they dont fully understand all changes and my suggestion doesnt influence the actual gameplay, so i assume i can post. im sorry if im wrong, then youre free to close.

main idea:
what i would like to see are some kind of counters for how many tickets were lost by what. for example: apc: 10 tickets (would mean 2 apcs went down), ifv: 10, inf: 123 (possibly split for dead-dead/wounded+revived).

implementation:
where and how you could add this counter, especially the display of them, might be a problem, but as i didnt work much with the bf2 engine, i dont have much a clue. people, who do might think about that.

reason:
there have been a lot of times i wondered how we lost so many tickets. especially in the last game in the tournament (on qwai) i really wondered (im not trying to disagree with catas win, they played better and won fair) where our tickets went.

possible problems:
haters. there will be whining about a certain asset sq losing a lot of tickets, but as there is no possibility to grief in a game deciding way and you simply can ignore them, it shouldnt be that much of a problem.

regards,
skull

have you read the manual? because ive seen somewhere about how many tickets you lose if you lose apc or die or whatever and it should be in the manual

Have you read the thread? because I think he's talkin about a counter INGAME, wich list the lost assets in real time during a game.

hi,

that is indeed what i meant, a real time in-game counter.

regards,
skull

i think it does record that to some sence IE:
In bf2 it registers like

Skull [M16] Wicca or smt means you killed me.

Might be possible with python to write a script that records ticket losses and what caused them, then display them at the end of the round?

Moved to suggestions, feel free to continue discussing when this forum is reopened

Wicca, I see your point, but I think Skull means a counter that shows how many tickets are lost when they are lost (for example, when a tank is blown up, there could be a notifier on the screen somewhere). I like this idea, but I ultimately don't think it is needed.

I really like the idea and is realistic, when someone joins the game especially if they're commander, they'll wnat to know the current vehical situation and how many they've lsot and vice versa.

I do not think it is completely necisarry, (spelling FTW), because we do not need another thing in the squad menu. This would be good for the end of a match though, it could be next to the scoreboard for each team showing how many of it's tickets were dedicated to each thing.

Taking this a bit further, I think it'd be a great idea to completely get rid of the score system as it is now, and replace it with a team-based score system, containing things such as number of firebases built, number of firebases destroyed, number of troops wounded, number of troops killed, number of troops that gave up, number of light / medium / heavy vehicles lost, number of transport / attack helicopters / jets / bombers lost, number of area attacks used, number of mortar shells fired, number of players including those who logged on and off, number of kit X, time spent in ticket bleed, tickets lost by losing flags, number of deaths by enemy fire, number of suicides/lethal accidents, number of friendly fire incidents, number of deaths due to rule violations (teamkill followed by kit pickup, not having a crewman/pilot kit, going out of bounds etc), number of enemies killed / arrested, number of civilians arrested, number of non-combatants killed within ROE, number of non-combatants killed outside of ROE and many more.

THAT'd be an interesting read, as opposed to the current scoreboard that basically just tells me who was transport vehicle driver/pilot or firebase-builder for most of the time.

hi again,

this kinda a bump, aswell ive gotten pretty curious about that idea, because i found a possible bug in the ticket loss system. (ill be talking to wicca which will hopefully redirect that to you).
still i like the idea and so seems everyone else, so lets implement it

regards,
skull

I always have a pen and paper with me in battles, its pretty easy just to watch the scoreboard also.

Spec Operator's idea is pretty interesting. I think it has been talked about before, no idea what happened to it though

Tim270 wrote:I always have a pen and paper with me in battles, its pretty easy just to watch the scoreboard also.

Okay...

What do you, write down?

We really need count ticket by ticket the enemy or we lost and why?

bump

approved? denied? anything?
just wanted to know cause im still curious about the issues stated in the first post.

regards,
skull

I really like the idea. I also would like to see each players ticket gain/loss ratio after a round ends (in the scoreboard), so the ticketwasters would feel some shame, after all they could be humans with feelings.

possible problems:
haters. there will be whining about a certain asset sq losing a lot of tickets, but as there is no possibility to grief in a game deciding way and you simply can ignore them, it shouldnt be that much of a problem.

From a different perspective: now you have proof that someone is wasting assets. What's still wrong with PR and is not "fixable" is the problem that there's always a player not caring about tickets and using assets like they are not supposed to or using assets they don't know how to use (choppers, jets). This player type can ruin a well played round for focused, ticket-counting players simply by loosing a lot of tickets.

Spec_Operator wrote:-snippity-

+9001 for this

Yes could be nice, even if it was available like BR, so if a server admin team wanted to (PRT) they could post it up after a round.

Would be nice on a squad basis, it'd be tricky on an individual basis.

Sq 1 1254 points 600 Build 404infkills 200assetkills 50Drive
Lost 600infkills 80assetkills

Very tricky to sort out what info to show from whats possible, would there not be a risk of more server instability?

Spec_Operator wrote:Taking this a bit further, I think it'd be a great idea to completely get rid of the score system as it is now, and replace it with a team-based score system, containing things such as number of firebases built, number of firebases destroyed, number of troops wounded, number of troops killed, number of troops that gave up, number of light / medium / heavy vehicles lost, number of transport / attack helicopters / jets / bombers lost, number of area attacks used, number of mortar shells fired, number of players including those who logged on and off, number of kit X, time spent in ticket bleed, tickets lost by losing flags, number of deaths by enemy fire, number of suicides/lethal accidents, number of friendly fire incidents, number of deaths due to rule violations (teamkill followed by kit pickup, not having a crewman/pilot kit, going out of bounds etc), number of enemies killed / arrested, number of civilians arrested, number of non-combatants killed within ROE, number of non-combatants killed outside of ROE and many more.

THAT'd be an interesting read, as opposed to the current scoreboard that basically just tells me who was transport vehicle driver/pilot or firebase-builder for most of the time.

please, yes!

That would be cool if there was an after action report program that could give you a list of times and assets lost during the game with a listing like

ankyle62(BMP) kills Noob
ankyle62(M16A2) kills Newb