Results 21 to 30 of 32
Thread: Documentation
-
17-04-2014, 22:19 #21Don't send me private messages (PMs) unless you really need privacy, like your game server password. If you just have a question or need help, post in one of the threads. It's extra work for me to answer questions and give help in private messages and no one else gets the benefit of the answer.
-
18-04-2014, 08:23 #22
Nick wants the gsp panel where to reset your instance to be https://farmland.myrcon.com. So that's happening as well.
I thought masher too, but I wanted to save that for something 'big', while peeler (or something like that) is used for something delicate while sticking with the theme.I started at DICE late Oct. 2014, so ignore every post before that.
-
18-04-2014, 11:09 #23
- Join Date
- Dec 2010
- Posts
- 1,031
sacks.myrcon.com is clearly the answer. Or a slight adaptation of nicks suggestion. Austria.myrcon.com
Sent from my Nexus 7
-
18-04-2014, 22:01 #24Don't send me private messages (PMs) unless you really need privacy, like your game server password. If you just have a question or need help, post in one of the threads. It's extra work for me to answer questions and give help in private messages and no one else gets the benefit of the answer.
-
21-04-2014, 02:44 #25
Update on various bits..
We're still sticking with procon.myrcon.com for the ui though. Since that is the product as a whole and we just needed a method to identify the two distinct sub-projects.
It may be shortened to farm.myrcon.com because shorter names are betterer.
I have not touched the docs in a few days. I may find some time tomorrow to just put in some links to examples on github with a one-liner about what they demonstrate.I started at DICE late Oct. 2014, so ignore every post before that.
-
21-04-2014, 17:30 #26Don't send me private messages (PMs) unless you really need privacy, like your game server password. If you just have a question or need help, post in one of the threads. It's extra work for me to answer questions and give help in private messages and no one else gets the benefit of the answer.
-
30-04-2014, 23:52 #27
I think you should reconsider your naming - very funny now but in the future will kill us all off.
Evidence of the difficulties we have now...
https://forum.myrcon.com/showthread....389#post102389
Imagine that discussion talking potatoes and peelers
-
01-05-2014, 03:30 #28
It's to separate the project during bug reports more than brand recognition. It's different enough from #1 that we need the distinction when people ask for support so we know what they are talking about.
We will have people say "I can't login to my Layer" referring to the peeler. It's inevitable.
I would also hope this iteration of the software isn't nearly as difficult to setup for end users.I started at DICE late Oct. 2014, so ignore every post before that.
-
01-05-2014, 19:01 #29
(I have a suspicion of being wound-up here, but in case it's legit ...)
You know, I think I disagree that peeler/potato will cause more confusion. I've often wanted to try commonplace names for technical concepts that tend to get overloaded onto existing names like "client" and "server", to give people at least a basic sense of the relationship between the two. Particularly when most people don't know the basic concepts, like client and server.
Potato and peeler do suggest a relationship that most English-speaking people will intuitively understand. There might be a danger of reading too much into it, of course, like, "Does the peeler remove my layer from the potato?" But I think I'd rather have that kind of confusion over endlessly explaining what UI vs Instance means.Don't send me private messages (PMs) unless you really need privacy, like your game server password. If you just have a question or need help, post in one of the threads. It's extra work for me to answer questions and give help in private messages and no one else gets the benefit of the answer.
-
01-05-2014, 23:53 #30
Me ? wind up ? I don't have time to joke about
though that thread is a classic and I think I can hear your head banging on the desk.
Surely you cant be serious, if host and client had been used in the beginning, then the discussions may have been a bit easier.
You setup your hosted/24 hour procon as a host - then you setup your home procon as a client which connects to your host procon
as opposed to:
You setup your hosted/24 hour procon as a layer, then you setup you home procon the same but connect to the layer procon
and now
You setup your hosted/24 hour potato, then you setup you home peeler the same but connect to the potato
And yes - I wont call you Shirli