[LE] How do I use a Keyword from another mod in my mod?

[PeterMartyr]

@IsharaMeradin

 

there is a lot coders mainly software developers, which is different from software engineer, and not all of us are great mathematicians, some us do even care about the behind the scenes working of a PC, Plus if you specialist in C++ and Game Engine for a few years,then you write a web app, as Game Developer writing a web app, I can I guarantee it'll get hacked so fast because of all the vulnerabilities because you're not up to date in what going on... That guy made a mistake... I do not care if he help develop papyrus, that hexadecimal is still wrong and against coding convention

[IsharaMeradin]

I do think there is something to be said for uniformity in numbers. If Bethesda truly did not want any leading zeros they would have truncated the form IDs in all instances. Instead, the Creation Kit shows the entire 8 digit ID number at all times. Look up any object within the in-game console and it displays the 8 digit ID number. Even third party utilities like xEdit will display and work with the entire 8 digit ID number.

 

Can we shorten it? Yes. Is it necessary to shorten it? No.

Can we argue about this? Yes. Is it necessary to argue about it? No.

[PeterMartyr]

Please do not think I am arguing, like I said the compiler does not care, :laugh: and like I said in my first post the zero get truncated, it more a human thing :cool: so yep agree to disagree.

Plus this discussion is good, once hexes get store in the memory, or a user uses getFormID, what come out is not what you think, so getting this out there, so the peeps are aware, cannot be a bad thing.

 

@readers not @IsharaMeradin

 

if you debug a form what is spat out is formatted string, not a hex as a number.

 

Papyrus is forgiving, most other languages are not, except javaScript, JavaScript is a loose like Papyrus, do not develop bad habits.

 

Plus I will be honest when I was learning Skyrim Papyrus, my Syntax Coloring did not work unless I truncated the Zero's in hexes, 0x00001b had to be 0x1b for the coloring to work. So I got started early on it. :pirate: But it got severely reinforced in uni, with the threat of a fail. One lecturer even threaten to fail us all if we concatenated a string the + operator. Once I unit tested concatenate strings, f*#@Ke Mee, that the worst thing in coding ever... I agree. Hopefully Bethesda will add a StringBuilder in starField, it will increase performance 10,000 fold regarding strings. Things are not what you think in the real world.

 

For example this really bad and consider high school level programming or teaching someone new who has never programmed

int nFormID = AkaviriKatana.GetFormID()

self.DecimalToHexadecimal(nFormID )

it should be like this

self.DecimalToHexadecimal(AkaviriKatana.GetFormID())

you get judge for style, I shite you not, version 1 is creating garbage for Windows to dispose of, version 2 is not. Even with a simple thing like that, there can be improvement. Knowing how your code affect the memory is important. Lots of little things add up to big things.