Author Topic: sysvars - The Official List  (Read 14306 times)

Offline Numsgil

  • Administrator
  • Bot God
  • *****
  • Posts: 7742
    • View Profile
Re: sysvars - The Official List
« Reply #15 on: October 12, 2013, 01:37:15 AM »
Yeah, no real rhyme or reason.  New features are sort of crammed in wherever there's free sysvars.

Offline Botsareus

  • Society makes it all backwards - there is a good reason for that
  • Bot God
  • *****
  • Posts: 4483
    • View Profile
Re: sysvars - The Official List
« Reply #16 on: October 12, 2013, 10:06:07 AM »
I can name one:

You will see that sysvars are grouped.

Like, movement sysvars are grouped 1 trough 6
Defense sysvars are grouped 820 trough 839.

This is not always the case. But this is the sysvar naming convention I am following. The mutator usually offsets a value rather then picking a new one. Hence the empty sysvars between sysvar groups serve there purpose on limiting really wild changes in robots behavior.



eh, never mind, I am repeating what has already been expressed. Sorry.

There is no rule on how far sysvar groups should be away from each other. That is true.

« Last Edit: October 12, 2013, 10:09:15 AM by Botsareus »

Offline Shadowgod2

  • Bot Destroyer
  • ***
  • Posts: 387
    • View Profile
Re: sysvars - The Official List
« Reply #17 on: October 13, 2013, 11:37:35 AM »
thanks it just makes larger bots harder to make, like a NNet bot that i am working on using as many memlocs as i can and not as many large openings as i wish there were

thanks for the info

Offline Botsareus

  • Society makes it all backwards - there is a good reason for that
  • Bot God
  • *****
  • Posts: 4483
    • View Profile
Re: sysvars - The Official List
« Reply #18 on: October 13, 2013, 03:11:09 PM »
I am also working on fixing epigenetic memory, the memory locations that are supposed to be copyied trough birth tie are not happening. This should help pass epigenetic information for your NN bot.

Offline Shadowgod2

  • Bot Destroyer
  • ***
  • Posts: 387
    • View Profile
Re: sysvars - The Official List
« Reply #19 on: October 13, 2013, 03:41:42 PM »
well the NNet bot will be using a lot more than epigenetic memory but that's interesting.

something i found in the wiki was that refvel and refvelup have the same memory location. is that true?

Edit: i just got an idea of teaching though it will be implemented later... if i complete it i wonder i it will discover/evolve/develop teaching on it's own before i put teaching in :thinkey:

Edit: never mind i get it now.
« Last Edit: October 13, 2013, 05:29:09 PM by Shadowgod2 »

Offline Numsgil

  • Administrator
  • Bot God
  • *****
  • Posts: 7742
    • View Profile
Re: sysvars - The Official List
« Reply #20 on: October 14, 2013, 02:00:27 PM »
Refvel is just shorthand for refvelup.  That is, it's not a mistake.  They're not supposed to be different. 

Offline Shadowgod2

  • Bot Destroyer
  • ***
  • Posts: 387
    • View Profile
Re: sysvars - The Official List
« Reply #21 on: October 15, 2013, 01:56:57 PM »
that's why i said never mind

I've just got an idea though about custom and sysvars:
 you could make it to where you could move sysvars around using something like a custom variables only using something different like redef

example is say redef up 5

it would use memory location 5 as .up and you could use memory location 1 as something else if you wanted. this way if you wanted to make a memory intensive bot without spreading everything out you could

Offline MacadamiaNuts

  • Bot Destroyer
  • ***
  • Posts: 273
    • View Profile
Re: sysvars - The Official List
« Reply #22 on: September 03, 2014, 06:16:14 AM »
Someone remind me again of how sysvars wrap around.

E.g. what does -193 or 1421 translate to.
Sometimes you win, and sometimes you lose...