here weapons.ini
Code: Select all
'sacc' =>
'lifetime' =>
'life' =>
'v' =>
'iheight' =>
'type' =>
'mrange' => ,
Code: Select all
'hp' => ,
'build' => ,
'prereq' => ''
Code: Select all
'sacc' =>
'lifetime' =>
'life' =>
'v' =>
'iheight' =>
'type' =>
'mrange' => ,
Code: Select all
'hp' => ,
'build' => ,
'prereq' => ''
my bad haha, stats from left are the one that will be put to guide page, while on right is comes from .ini. but some stats either not entered in ini file or have a different name and it's pretty confusing so i might entered wrong stats from ini file to guide page like 'direction' => simplify($tvals['facePlayer']), which should be 'movement' (i fixed it already).Per wrote:I don't understand your question.
seems those don't do anything, but we have longRange (i use this for long range),longHit (i use this for log accuracy) but we dont have shortRange and shortHit in weapon.iniPer wrote:I can tell you what every line in the .ini files is for, but I can't tell you what 'v' in a php script I've never read is...
Hi Per, if you project still needs converter from txt to ini I can rewrite it in python. I think old one is outdated since we rename/remove some fields and simplify some files.Per wrote:I can tell you what every line in the .ini files is for, but I can't tell you what 'v' in a php script I've never read is...
Send me PM what to what. Or just do something and send result?Per wrote:That would be useful. As you can see, we still have a few .txt files remaining. Any help transforming those to .ini would be appreciated.
In what format attach it to bugtracker?Per wrote:Do something and post result in bug tracker.
Just attach the .ini files you have made to the bugtracker. Your first attempt looks good. I'd like to see just one change, see below.Duha wrote:In what format attach it to bugtracker?
Just leave functions.txt to me, I am working on that right now. Its contents will be moved elsewhere.Duha wrote: I don`t know waht to do with function. Should I merge them to researches?
I'll look into it.Duha wrote: I don`t know what to do with template.avaliable (for base it has 7, 5 and other values for mp it is yes/no)
Yes, please.Duha wrote:May be we should merge assignweapons to templates?
http://developer.wz2100.net/ticket/4005Per wrote:Just attach the .ini files you have made to the bugtracker. Your first attempt looks good. I'd like to see just one change, see below.Duha wrote:In what format attach it to bugtracker?
Per wrote:Nice work. While you're at it, maybe you can write a script to transform from old functions.txt + new research.ini resultFunctions to even newer functions line in research.ini?
Here is how it looks in upgrades branch: https://github.com/perim/warzone2100/bl ... search.ini
Notice the lines with 'results' keys.
Here is how it looks previously: https://github.com/perim/warzone2100/bl ... search.ini and https://github.com/perim/warzone2100/bl ... ctions.txt (yes, functions.txt is removed entirely in upgrades branch)
I changed the MP research.ini by hand. This was a ton of work, and may have mistakes. If you could write a script to change base and mp automatically, I would be very grateful.
Code: Select all
{
'Research Upgrade': 'ResearchPoints',
}