Help with a couple of things

[kennethwsmith]

Hey Angel, I was hoping in your spare time you might be able to explain a few things. I am really new to react and was trying to add a few things in slowly to the tool. Also, if there is anything you think I implemented wrong please don't hesitate to reject my pull request, it wont hurt my feelings. :)

So i wanted to add Hacknet hash capacity and Hacknet hash count to the PlayerSave page. Here is my code to add it:

     <div className="flex flex-wrap gap-4">
        <EditableSection
          type="number"
          label="Hacknet Hash Capacity"
          property="hashManager.data.capacity"
          value={player.data.hashManager.data.capacity}
          onSubmit={onSubmit}
        />
      </div>
      <div className="flex flex-wrap gap-4">
        <EditableSection
          type="number"
          label="Hacknet Hashes"
          property="hashManager.data.hashes"
          value={player.data.hashManager.data.hashes}
          onSubmit={onSubmit}
        />
      </div>

I think everything except the property is right. My save file ends up with 2 new root entities: "hashManager.data.hashes" and "hashManager.data.capacity" instead of updating the hashManager object.

I tried playing with the "updatePlayer" method in file.store.ts but everything I did just blew it up.
Also, is there a document on the design pattern you used here, or is this "vanilla react" and I just need to read more.

Thanks for the help!
Ken

[kennethwsmith]

Second question, when you get a chance do you think you could help me with a simple example for creating a checkbox for boolean properties? "has4SData" would be a good example. I have been looking through the faction code but it is escaping me on how it is done.

[Redmega]

While it's all essentially "vanilla react" I did some abstractions to allow certain components (EditableSection, for example) to be used in multiple use cases (various value types, properties, etc) in an effort to not have a single component per property.

Re: Hacknet hashes, etc. I'll have to look into it, it's also possible that these are derived values and can't be directly modified. See how we handle EXP and skill levels for an example of weird stuff I had to do to get it to work. Technically if I make a skill level X, it won't work because the game automatically recalculates the level based on the EXP and multipliers for that skill. So I ended up having to work in some custom logic to handle that data relationship.