Nova Sector 13 - User contributions [en]

Guide to setting up your coding environment and How To Run A Test Server

2024-07-26T20:02:11Z

GoldenAlpharex: Capitalization in headers

==GitHub==
If you don't have a GitHub account, start by making one.
Then, you go to the repository on GitHub, which can be found here: https://github.com/NovaSector/NovaSector
You should see the buttons displayed in the following image on the top-right-corner, you want to click on the one that says "Fork". 
<tab name="Click here to reveal image" collapsed>
[[File:Server setup example 1.png]]
</tab>
Once you've done that, it should take you to your own fork of the repository. That means it's your semi-independent version of our codebase, on which you're free to do whatever you want. You should find it at https://github.com/yourgithubusername/NovaSector, like this: https://github.com/GoldenAlpharex/NovaSector
==VSC and GitHub Setup==
Now, what you want to do is two things: Download Visual Studio Code (VSC) and GitHub Desktop (you could use something else, but that's the easiest to work with when you're new). When setting up Visual Studio Code, I highly suggest you check the option that makes it so you can open folders in VSC from the options that pop up when your right-click on a folder in the file explorer, it'll make your life easier. Links for VSC and GitHub Desktop: 
https://code.visualstudio.com/ 
https://desktop.github.com/

Then, once you've downloaded both, you want to go to the page of your fork that I mentioned earlier (https://github.com/yourusername/NovaSector)
You want to find this big green button on the main page, and then click on it, and then click "Open with GitHub Desktop". 
<tab name="Click here to reveal image" collapsed>
[[File:Server setup example 2.png]]
</tab>
It should open your GitHub Desktop and basically ask you to identify yourself if it's the first time you're opening the application, and then it will ask you for details for where you want the folder to be, just set yourself a folder for all of your GitHub repositories somewhere and then just click "Clone" whenever you're satisfied with everything. Then, it's a waiting game, waiting for the cloning to be done.

Once it's done cloning, it should look like this:
<tab name="Click here to reveal image" collapsed>
[[File:Server setup example 3.png]]
</tab>
You'll want to click on Repository > Open in Visual Studio Code, like this: 
<tab name="Click here to reveal image" collapsed>
[[File:Server setup example 4.png]]
</tab>
It will bring you to Visual Studio Code. In the bottom-right corner, it will suggest you some extensions to download. You need to download at least the two BYOND-related extensions it suggests (DreamMaker Language Client and BYOND DM Language Support), which also have the benefit of making your life a whole ton easier. You need to restart VSC to get the extensions to work.

Once you're done, you should be able to see this on the right of your editor (with less buttons because I have more extensions). You want to click on the one that's circled. 
<tab name="Click here to reveal image" collapsed>
[[File:Server setup example 5.png]]
</tab>
You will get to this page, on the right still, you go to the top of it and click on the downward arrow and select "Launch DreamDaemon" (so you don't run out of memory during your testing, because yes that's a problem now) 
<tab name="Click here to reveal image" collapsed>
[[File:Server setup example 6.png]]
</tab>
Then, go at the bottom and untick the "Runtime errors" breakpoints (CAUTION: IF YOU'RE CODING, TURN THIS BACK ON, THIS IS JUST TO MAKE IT EASIER WHEN YOU'RE NOT CODING AND WANT TO HOST A SERVER QUICK 'N EASY FROM A WORKING CODEBASE!) 
<tab name="Click here to reveal image" collapsed>
[[File:Server setup example 7.png]]
</tab>
==Server Setup==
Now, you're ready to start your test server! Simply hit F5 and let everything compile! If there's compile errors that are not DM-related, it's likely because you're missing some things that you have to download and it should usually tell you what you need to install. The end result should look roughly like this: 
<tab name="Click here to reveal image" collapsed>
[[File:Server setup example 8.png]]
</tab>
Now, it should open Dream Daemon, if it doesn't pop up, go to your taskbar's "Show Hidden Icons" button and right-click the green BYOND icon, then click "Open Dream Daemon".
You should see this, the IP I blacked out would be your IP, and you can se the port if you want this to be actually public. However, I recommend setting the visibility to "Private" just so you don't have someone random joining your server.
To join your own server, you can click on the button that's circled in red in the following picture: 
<tab name="Click here to reveal image" collapsed>
[[File:Server setup example 9.png]]
</tab>
It should now have opened your very own private server, on which you have full Host powers without any setting up required.

Enjoy!

Fundamentals for Players

2024-07-23T23:18:45Z

GoldenAlpharex: Updated some old links so that they'd point to the right place.

{{Rules navbar}}
=Introduction to Nova Sector=
[[File:NovaSectorAnimatedTransOptimized-ezgif.com-resize.gif|250x250px]]

'''Welcome to Nova Sector!'''

==Tidbits to Remember:==
*'''We are not a "Furry TG" server.'''
**'''While we act as a downstream of their excellent codebase, our goals differ significantly from theirs, favoring RP over 'disaster survival.''''

*We do not expect new players to know every rule right away, just to work with staff if you happen to break them.

*Nova Sector Main should be treated as a roleplaying server, not to be appended with the titles other servers like to brand themselves with. (LRP, MRP, HRP.)

'''Be respectful of others.'''

=Recommended Reading!=
To get off on the right foot in both the application process and our server, please follow the following list and read the documents provided.

A basic understanding of the required documents is required in order to gain entry into the server:

#'''Community Rules: [https://discord.com/channels/1171566433923239977/1172988364513882312/1187825661709123684 Here!]'''
#'''Server Rules:''' [[Server Rules|Nova Sector 13 Ruleset]] and [https://discord.com/channels/1171566433923239977/1172988371098931360/1172989744578314270 Rulings] - The idea is to get a basic overview of what is and what is not allowed. Most are just common sense.
#'''General Player Policy & Standards:''' [[General Player Policy and Standards]]
#'''Read our ERP Courtesy Policy:''' [[Misc Roleplaying Policy|Miscellaneous Roleplaying Policy]]
#'''Thoroughly read our Action-RP Lawset:''' (see below)

=Action-RP Lawset=
===0. Definition===
'''Play-to-Win Mechanics'''

* The term "Play-to-win-mechanics" describes when a player engages with the game mechanics with the intent of creating an advantage for themselves in an attempt to 'win', but at the cost of the quality of roleplay, and, while negatively affecting the experience of others.

What differentiates ''using mechanics to roleplay versus using mechanics to 'win''' is the follow-up.

* Shoving past someone with a lead up emote, without a follow up, or running away, is within roleplay: whereas shoving them randomly, and running off immediately, is not.

'''However;''' know that the onus of making it clear you're not playing to win, is on you, and if it's not clear, be aware you will be open to CI-without-wait retaliation.

===1. Combat Indicator===
[[File:CI.png]]

'''^ This ^ is what the combat indicator looks like.'''

* Combat indicators signal the transitioning from roleplay to the start of 'combat.'
** Think of it as a handshake that should be returned by the other party, so that people cannot get the jump on someone who is typing, and or not paying attention.
** After activating CI, you're required to wait atleast four seconds if they don't CI back, or two seconds if they do, this applies to everyone involved.
* '''If the other person is still roleplaying, and the situation and or escalation permits, you can attack once the four seconds pass, even if they don't CI back.'''

====Important Notes:====

*If you or your target is in the middle of active mechanics, (already fighting, running away, trying to break/get into somewhere, or away, etc.), you do not have to wait the grace period, although you should still turn on the combat indicator.
*You must wait the required grace period or until the other party has their combat indicator turned on.
*Actions done without intent to gain an advantage, shoving, pieing someone, knocking someone off of a table, etc leave yourself open to immediate retort.
**If done for an advantage (pie>trying to shove them into disposals) CI is required.
*Do not preload combat indicators, or continue roleplaying after turning them on. Use it or lose it.

====Example Scenarios====
''Remember - Combat Indicator or CI must be turned on first before the grace period timer begins.''

# If either party is in roleplay, you should always attempt to roleplay the escalation first, if they try to disengage from the roleplay(start hacking the door to get out, get a weapon out without an emote doing so, etc) you're free to attack as they have actively started mechanics.
# If something is forcing mechanics, i.e. another player, an event like depressurization, and so forth, you are free to engage in mechanics. Though you should still CI.

===2. When to Role-play, When to Mechanic===
If you are in a roleplay, you should assume roleplay, i.e. saying and emoting, by default, until roleplay dictates that mechanics are needed to advance a scene or if mechanics.

If you intend to call for backup, or else-wise, drag more people into an escalating situation, it will be considered mechanics for application of CI.

Keep in mind that mechanics serve the overarching story and the roleplay contained within, not the other way around. Mechanics are here to make the roleplaying experience more real, not prohibit it from happening.

===3. Conduct During Ongoing Scene===
If a roleplaying scene is present, you should try to believably escalate the situation, before starting mechanics.

===4. React and De-escalate===
React to mechanics by mechanics, i.e. individual is running away, however, look to de-escalate to roleplay when able, after 'mechanics' (the fight, w/e) has concluded.

===5. No Unnecessary Round Removal.===
Do not unnecessarily take someone out of the round. There are no mechanical advantages for round removal. When a player gets killed and then revived, they are not allowed to remember their attackers or how they were attacked.

===6. Cooperation===
Why do we have all this? Well, at the end of the day, roleplay is a cooperative affair. It is not competitive where you are looking to create an edge for yourself. Rather, it is a community affair where you work together to craft stories for yourself and the group at large.

Equally, you should make use of LOOC to make intents clear when able, in unclear situations (someone about to shoot someone else in the back, mid conversation.) so everyone is on the same page about how a situation is escalating.{{Rules table}}
[[Category:Rules]]