(un-)popular opinions: Difference between revisions

From Resonite Wiki
change link to slot count
fix link
Line 24: Line 24:
# [[ProtoFlux]] is actually very straightforward and easy to learn.
# [[ProtoFlux]] is actually very straightforward and easy to learn.
# You should use [[Things to Avoid|Ref Hacking]] to spice up all your creations as it is a very exciting [[wikipedia:Blockchain|technology]].
# You should use [[Things to Avoid|Ref Hacking]] to spice up all your creations as it is a very exciting [[wikipedia:Blockchain|technology]].
# There is [[:Category:ProtoFlux:All|functions]] that you can [[Type:Call|call]].
# There is [[:Category:ProtoFlux:All|functions]] that you can [[Impulses|call]].
# The [[StripeWireMesh_(Component)|spaghetti]] between the nodes is actually edible.
# The [[StripeWireMesh_(Component)|spaghetti]] between the nodes is actually edible.



Revision as of 15:23, 3 March 2024

Not to be confused with Hot takes.

Introduction

This page chronicles all the (un-)popular opinions about Resonite and the things inside it.

This page is an example of humor. Do not believe anything you read on it.

General Opinions

  1. The Resonite logo is called a Gloopie.
  2. 7 is not a number, it is actually a type of cheese.
  3. Motion blur is fine and justified, actually.
  4. A Resonite is a way to to play the clarinet.
  5. This page took way too long to make.

Etiquette Opinions

  1. Do not touch my Flux or I will shoot you.
  2. "Touching yourself is not currently supported in Resonite." - Frooxius[Citation needed]

ProtoFlux Opinions

  1. ProtoFlux is actually very straightforward and easy to learn.
  2. You should use Ref Hacking to spice up all your creations as it is a very exciting technology.
  3. There is functions that you can call.
  4. The spaghetti between the nodes is actually edible.

Avatar Opinions

  1. The default avatar should[1] have cat ears.
  2. Slot Count is the sole and only metric of an avatar's performance and should be kept below 50 at all times
  1. The word 'should' is to be interpreted as described in RFC 2119.