LUA Enchangements

[MuwuM]

Hello,
I will build some new LUA functions in near future.

Here all new functions, that are done so far:

SVN rev 2767:
displayFormattedLangText ()

SVN rev 2813:
addConsoleLangText()

SVN rev 2823:
new events:
    unitAttacked (by softcoder)
   unitAttacking (by softcoder)
 
   methods:
   lastAttackedUnitName() (by softcoder)
   lastAttackedUnit() (by softcoder)
   lastAttackingUnitName() (by softcoder)
   lastAttackingUnit() (by softcoder)
   giveKills(unit,amount)

SVN rev 2824:
new lua method (by softcoder)
lastDeadUnitCauseOfDeath(),
possible int values are:
   None = 0
   Attacked = 1
   AttackBoost = 2
   StarvedResource = 3
   StarvedRegeneration = 4
 

[Omega]

Before it's too late, I'd like to point out that for consistency, the function name should be displayFormattedLangText() (with the first letter being lowercase). I think that since all modders would have access to these functions, it's very important that the naming format of functions is the same, even if that doesn't match the individual codder's preferences.

For example, if we had most functions in the format camelCaseIsCool, but then someone makes a new function slightly different like FirstLetterCapitalized, and then maybe someone else would even get to the point of which we have i_prefer_underscores... It just gets a horrible mess for modders, who often would memorize function names based on the content only, not the casing.

[MuwuM]

I'm sorry, but I used the same capitalizion as in DisplayFormattedText(). So for me no obvious syntax exist.

[Omega]

I'm sorry, but I used the same capitalizion as in DisplayFormattedText(). So for me no obvious syntax exist.

Hmm... Strange. Looking at MG/Scripted Scenarios on the Wiki, every function EXCEPT DisplayFormattedText is in the format camelCaseRocks(). I think that DisplayFormattedText should work as either (and remove reference to the uppercase version on the wiki) for these same consistency issues I mentioned.

The wiki lists 52 different MegaGlest Lua functions, of which 51 are in the same consistent format, and 1 is not. Seems a bit redundant?

The majority of times (that I've seen), camel case is written with the first word all lowercase, that way a single variable (eg, "foo") will be a far more standardized lowercase instead of "Foo". Some instances it does appear with the first word capitalized as well, though.

[MuwuM]

Well, I really don't have a Problem with lowercase at first letter, but maybe it would be better to make displayFormattedtext() lowercase, too.

[softcoder]

Done, that stray method is now in camelcase.

[MuwuM]

My Lua function is now camelcase, too. It's now in SVN head. 

Next function will be: addConsoleLangText() wich will be the same as addConsoleText() besides the fact, that it allows variables like displayFormattedText ().

Function is Done. Now testing. Will obvious be in next dev-version (after recent beta).

Third function will be a fuction which resolves unit-names e.g. resolveUnitName("test_unit") will return "Test Unit".

Function-list updated (new beta site added) https://docs.megaglest.org/MG/Scripted_Scenarios_Beta