Project Reality Forums

I've been inactive for quite some time as I was afflicted with that annoying and time-stealing virus dubbed "Real Life", so forgive me for not being up to date.
What's the status on the official PR wiki? Last I heard (which is almost over a year ago now), there were plans to reactivate the official wiki. Which was the reason we stopped working on our wiki in the first place. Has this happened, will this happen?

If not or only in the far future: Is there an interest for us to update our wiki to PR 1.0? Updating the technical info is fairly easy, as I just have to re-run all the parser scripts, but updating images, maps and adding the entirely new content would take days again, so I'd rather try and see if there's an actual demand.
I'm also open to suggestions to convert our wiki project into an official wiki, if the devs have an interest in that?

An updated Version of your Wiki would be nice! Please do it!

If you want to contribute, you can do so here.

I will add all the editor codes there over the next days (see the multiple sheets of the spreadsheet), and I need proper names for all of them. Currently we aim for English and German, so those names would be most welcome. While you certainly can add other languages as well, I cannot guarantee there'll be a use in the wiki for those right now.

Guidelines are:
- Missing name cells are marked in orange, so gaps are easier to find.
- If multiple codes fit to a single name, just make the cell big (see the Factions tab for how I did this).
- Weapon names should be as short and precise as possible. They usually are a combination of "producer and object name", e.g. "Colt M4A1". If the Producer's name is long, try to use a shortcut ("Heckler& Koch P8" could be shortended to "HK P8", for example)
- Vehicle names should NOT include the developer. Instead - if applicable - they certainly can contain nicknames and model names such as UH-60 "Blackhawk", AW101 "Merlin" etc.
- If you have a name that most certainly should not be disrupted by a line break, you can use   to place a protected whitespace. This will tell the wiki to never automatically place a linebreak here. Example: "Heckler & Koch" is a name on its own, so it should never really be split. So use "Heckler & Koch".

If you want to contribute more, feel free to contact me in Skype, where we can establish a wiki group chat.
Skype handle is wgpsenshi.

I added all hand weapon codes now. They are categorized in different sheets. Another spreadsheet for vehicles soon will be added as well.

As I know that figuring out the actual weapon names can be difficult using the codes alone, I have extracted the texture atlas files, zipped them up and made available for download here.
Each icon is named with the weapon's editorcode, so you can either use the name pictured there directly or at least have it way easier to research the correct weapon type.

If you find weapons that I have put into a wrong category, please tell me as well.

Some weapons are unfinished/unused (Fusrodah , anyone?), those can be found in the "Unsorted" category/sheet.

Thank you to everyone that helps with this , allows me to focus on refining my parser program that is supposed to do all the rest of the work.

Necro inbound.

I'm once again in the process of updating the wiki. My data parser tool is coming along nicely and it can compile the kit and weapon lists "fully automatic" as well as give some nice advanced direct comparison in the tool itself. I certainly don't want to redo all this updating manually after every update, especially given how "precise" the changelogs are.

Next step is some manual cleanup to get all the red link-icons in the kit tables redirected properly, but that's easy to do. Then only the weapon tables are left to generate as well as the vehicles (the biggest task, really...).

By now my tool has grown so much it actually might be of use for mod devs or hardcore-data-diggers. While it's developed and tested for PR, all it does is to read and "understand" the bf2 data files and compile useful DBs (sounds much easier than it really is). Those DBs then can handily be searched/exported in a plethora of ways and levels of detail.
Currently it reads kits, handweapons, projectiles, materials, decompiles the menuatlas files (all the interface icons) and offers a minimap viewer with selectable overlay information.

Nice, I was going to something like this but dropped the idea.

Will this program give damage models? Like compare tanks and see what kind of damage can each one do in the different areas?
A good source to understand could be this, link.

I know how the damagesystem works in most parts, but thanks for the link.
The DB setup is all there for the damage calculations, I'd just have to create a GUI part for it. Another weekend's work I guess, but definitely intend to do that. Especially as that is super simple to do compared to the actual data parsing which has to account for every single typo and convoluted method that BF uses. I'm also considering porting those more "fiddling" parts to a Javascript-based webpage that allows everyone to fiddle without requiring the full tool. But yeah...that's further away still. First priority is getting the wiki fully up to date.

It's a great job bro.
Hope to see Multilanguage version sooner.

Ye Senshi, let us know if you need help with translation or other stuff.

A good portion is already updated to 1.1.4 thanks to my EMA tool. Just to let you know .

Looking great (I understand nothing at all )

How is the translation going? need help there?

Thanks for the kind words . As you posted here, I take it you don't understand the wiki? I'm not sure I can make a special Nate-friendly "stupid" version of that, sorry .
If you meant the tool, you should have written in the tool's thread. I tried to make it more userfriendly with the special "non-programmer" section . But I guess people still are scared of it. Only the bold will profit.

Translation is still not the issue, considering there's hardly any text to translate anyway (writing the texts in the wiki compared to writing the templates and the tool took about 1-2% of my time).. The issue is we still don't have a multilanguage wiki set up. It's not as easy to do as it might seem, and our webadmin is busy with his honeymoon . But I'm beginning to consider to just drop the German version entirely and switch to English. Everybody knows the rudimentary English needed to grasp the wiki anyway...

Ye I was talking about your tool, not the Wiki.

As for translation, I think an english wiki is better.
I checked your google sheet and there is still some stuff missing so I assumed translating would be necessary and asked

Translation still is necessary and very appreciated , but I was just saying there's not much point in translating texts right now. The google sheet is for the coded weapons, and that will definitely be needed! If you want and can add to that, feel free to do so, it really is very much appreciated.

Pls fix it, website is not loading... -.-

Nice work! The wiki looks really nice.

Some bugs I noticed:
Map Beirut: Assault and Secure Alternative posted 2x
Map Black Gold: Assault and Secure Infantry posted 2x
Assault and Secure Large posted 2x


I didn't check any other maps but someone/you might have a look at this... there seems to be something wrong either with your parser or the interface (I just assume you coded one ) for the wiki.

@Daniel: Not sure what's happening. It works for me and apparently for others as well. Are you sure you follow the correct link?
PR ? WGPWiki

@rep: Thanks for the feedback! It seems my parser processes the AAS modes twice and skips the Coop modes entirely there. Some weird fubar, I guess. Will look at it soon.

Two quick bugs I noticed as well:
- Shijia Valley only shows one skirmish layer and there are actually 3
- Khamisiyah shows the wrong factions for insurgency layers

Hope that helps. Great tool... and yes, I could definitely see myself using this tool when tweaking assets on map layers. Nice job so far!

PR:Bundeswehr ? WGPWiki

WOW is that website slow... I click on that link and it loads for 15 sec. and then finally all results come (before that, NOTHING! )

Daniel I just tried with the (slow) university-network wifi and it loads rightaway.