引用自 Blueshy：

引用自 1 regex = 1 a-z+：

With regards to editing/exporting, correct me if I'm wrong, I believe it's not really necessary as you can easily edit plaintext with programs like Notepad++?

Right, but if you for example wanted to increase the range of all the 9mm ammo you would have to go into the ammo theater and manually compute and change the numbers for each and every variant. Instead, you could simply add a command to multiply the current range values by 1.1 for all 9mm and then output a new ammo theater file. It will save you a ton of work and make tweaking groups of numbers much easier.

Ah I see. My script doesn't save the data hierarchy so that will take some thinking.

Btw, I noticed there are duplicate ammo entries in the srnx_common_ammo.theater

Edit: I wrote my script based on the indentation level and some of the tabs are spaces fml

First visualization: https://docs.google.com/spreadsheets/d/1W1K8PdB2USbGuq5WbonmMma9XPVBK6WO73FoI9XuM80/edit?usp=sharing

Idk what to comment on this, some rows are not in the game and have to be removed manually.

引用自 Daimyo：

Wow this is great.. I wish I invested time in the beginning to create a script that would cull all the data for easier exports after changes. I think one for Ammo would be YUGE in regards to revamping it or visualizing it.

I wonder how hard it would be to reverse import the data once changed.

Ammo? I'll have a look.

引用自 Blueshy：

Yeah, I think this is the way it should be done. The plain text theater files should be auto generated by scripts so that changing one variable can easily cascade through all the files and you just output a brand new set of relevent theater files each time. You shouldn't need to reverse import the theater files after a change.

With regards to editing/exporting, correct me if I'm wrong, I believe it's not really necessary as you can easily edit plaintext with programs like Notepad++?

引用自 Blueshy：

引用自 1 regex = 1 a-z+：

Now there's a bunch of missing data I filled in with the placeholder 'NA'. I guess these values come from the import?

Nicely done. For RPM, all those weapons with NA use "fire_cycle" (pretty sure it's inverse of number of shots per second) for their RPM instead of "rounds_per_minute".That's why your script couldn't find a value. For reload speeds, I'm guessing it comes from the actual animation file itself? The other catigories that have NA appear to be special use cases of variables. It looks like you have the majority of the useful data in there already. Might have to fill some stuff in manually though. Very interested to see what you do with that data!

My idea as fleshed out in the other thread was to get a geometric mean of all the metrics and hopefully get some useful visualizations. The problem is, you can't multiply by zero or NA. Maybe I'll work on splitting those recoil values for now.

The data is presented here to anyone who wants to do fun stuff with excel!

引用自 Blueshy：

引用自 1 share = 1 covfefe：

I might try it with python if the data is all in plaintext

Probably would work, I used a matlab script to redo the ammo descriptions file.

Thanks for the help, I managed to grab all the data using python and regular expressions. Now there's a bunch of missing data I filled in with the placeholder 'NA'. I guess these values come from the import?
https://docs.google.com/spreadsheets/d/1sDRbwlQFqGObNpFGNaJv-oZSXvrQrUh97uLvOHZI-LA/edit?usp=sharing

Ideally you could throw everything together if you use the geometric mean of all the damage values for each ammo type and body part, I think

I was reading about something called a Geometric Mean recently, and I realised it could help us look at the weapons from a purely quantitative standpoint.

What I mean is that if you say x gun has a higher damage so you increase the recoil and scope-in it's pretty intuitive, but what if the guns are all in the same "bracket" like all the 556 guns?

Therefore we can take the geometric mean of certain metrics such as the reload speed etc to get a rough idea of the standing of a gun. Thoughts?

Edit: I have extracted the data to a spreadsheet using a python script that recognises the weapon name header and extracts all key-data pairs below it.
https://docs.google.com/spreadsheets/d/1sDRbwlQFqGObNpFGNaJv-oZSXvrQrUh97uLvOHZI-LA/edit?usp=sharing
Some keys don't have values for certain guns and I'm unsure what to do now.

Maybe it just happens that the spawns are easily blocked by advancing players

The bots just spawn in a single location and get spawnkilled.

I remember that (fixed) bug where you could join the bot team with a console command.

引用自 Max：

I say yes to this. As much as I like the juggs....its too quiet. No loud explosions and I miss the loud sighing, "fucking ieds" comments etc etc....especially if juggs are to be nerfed more. Having them come out together will be a perfect mixture of chaos.

👍😎👌