armstrongl
commented
1 year ago Hi @JakeUskoski, thanks for all the feedback. I'm working on a PR to implement these fixes now.
Here's what I have so far:
- I corrected the Installation link.
- I looked into the command line helper link. It works on my end, but we've been receiving a lot of complaints about URLs breaking for one reason or another. We're investigating it, and it looks like it's either an issue with Docusarus or our pipeline. Sometimes Docusarus wants the filename, sometimes it wants the file ID, sometimes it appends
index.htmlto the end of the URL (and sometimes this results in the URL working; other times it breaks it). - I went through the doc and we do say to place scripts in the
Scriptsfolder, but we don't mention that the user needs to create this folder. To make it clear, I added a note at the top of the document saying to create theScriptsfolder.
Collecting a few points of feedback into a single ticket to save some time (from this slack thread). A coworker and I are going through the tutorials to get familiar with NGO for our hackweek project.
Doing the Netcode for GameObjects (NGO) tutorial. The link on the getting started page for installing NGO (included in the screenshot) links to a 404. It’s going to this bad link instead of (what I believe is) the correct link.
There’s a step which talks about using the command line helper to start the builds for testing. If you click on this link, it takes you to a 404 page, but if you right-click it and open in new tab (or cmd + click it), the link redirects to the correct page. I’m using Safari, and the other person on my team is using chrome. This is the section where it’s broken. On my coworker’s 2 laptops one has the latest version of chrome and the other has an older version of chrome. On the newer version of chrome the link goes to a 404, while on the older chrome version it works normally. The link is: https://docs-multiplayer.unity3d.com/netcode/current/tutorials/get-started-ngo/command-line-helper While the resolved path is: https://docs-multiplayer.unity3d.com/netcode/current/tutorials/command-line-helper/index.html
Additional feedback, more of a nit/comment: the getting started page instructs the user to create scripts directly in the Assets folder, while other tutorials (including the command line helper tutorial it tells you to follow mid-getting-started) tell you to first create a Scripts folder to put scripts into.