The following warnings occurred:
Warning [2] Undefined variable $awaitingusers - Line: 33 - File: global.php(779) : eval()'d code PHP 8.2.20 (Linux)
File Line Function
/global.php(779) : eval()'d code 33 errorHandler->error
/global.php 779 eval
/showthread.php 24 require_once
Warning [2] Undefined array key "style" - Line: 837 - File: global.php PHP 8.2.20 (Linux)
File Line Function
/global.php 837 errorHandler->error
/showthread.php 24 require_once
Warning [2] Undefined property: MyLanguage::$lang_select_default - Line: 4976 - File: inc/functions.php PHP 8.2.20 (Linux)
File Line Function
/inc/functions.php 4976 errorHandler->error
/global.php 837 build_theme_select
/showthread.php 24 require_once
Warning [2] Undefined array key 1 - Line: 1394 - File: inc/functions.php PHP 8.2.20 (Linux)
File Line Function
/inc/functions.php 1394 errorHandler->error
/inc/functions.php 1359 fetch_forum_permissions
/inc/functions.php 2862 forum_permissions
/showthread.php 618 build_forum_jump
Warning [2] Undefined array key "mybb" - Line: 1907 - File: inc/functions.php PHP 8.2.20 (Linux)
File Line Function
/inc/functions.php 1907 errorHandler->error
/inc/functions_indicators.php 41 my_set_array_cookie
/showthread.php 626 mark_thread_read
Warning [2] Undefined property: MyLanguage::$ratings_update_error - Line: 5 - File: showthread.php(729) : eval()'d code PHP 8.2.20 (Linux)
File Line Function
/showthread.php(729) : eval()'d code 5 errorHandler->error
/showthread.php 729 eval
Warning [2] Undefined array key "additionalgroups" - Line: 6872 - File: inc/functions.php PHP 8.2.20 (Linux)
File Line Function
/inc/functions.php 6872 errorHandler->error
/inc/functions_user.php 735 is_member
/inc/functions_post.php 403 purgespammer_show
/showthread.php 1063 build_postbit
Warning [2] Undefined array key "profilefield" - Line: 6 - File: inc/functions_post.php(471) : eval()'d code PHP 8.2.20 (Linux)
File Line Function
/inc/functions_post.php(471) : eval()'d code 6 errorHandler->error
/inc/functions_post.php 471 eval
/showthread.php 1063 build_postbit
Warning [2] Undefined array key "canonlyreplyownthreads" - Line: 646 - File: inc/functions_post.php PHP 8.2.20 (Linux)
File Line Function
/inc/functions_post.php 646 errorHandler->error
/showthread.php 1063 build_postbit
Warning [2] Undefined array key "showimages" - Line: 704 - File: inc/functions_post.php PHP 8.2.20 (Linux)
File Line Function
/inc/functions_post.php 704 errorHandler->error
/showthread.php 1063 build_postbit
Warning [2] Undefined array key "showvideos" - Line: 709 - File: inc/functions_post.php PHP 8.2.20 (Linux)
File Line Function
/inc/functions_post.php 709 errorHandler->error
/showthread.php 1063 build_postbit
Warning [2] Undefined array key "invisible" - Line: 1497 - File: showthread.php PHP 8.2.20 (Linux)
File Line Function
/showthread.php 1497 errorHandler->error
Warning [2] Undefined variable $threadnotesbox - Line: 30 - File: showthread.php(1524) : eval()'d code PHP 8.2.20 (Linux)
File Line Function
/showthread.php(1524) : eval()'d code 30 errorHandler->error
/showthread.php 1524 eval




Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Server tribe ideas.
#1
Revised version -> 29-08-2015 :

Sometimes in light of reflection one sees potential improvements upon ideas.


Server admin creates -one tribe-, lets call it tribe " X " for now.

Having -1- not -2- tribes makes it less work to administrate, solves the leadership problem, solves the issue of tribe vs tribe if or when theres an pvp situation.

Tribe " X " get following governance settings, to ensure that everyone own their personal stuff and no one else can steal from others :


# Dino taming :
  • --- Tribe taming
  • *** Personal taming
  • ^ Meaning any dino must be tamed by the player and is from then owned by the player and cannot be loaned or stolen by another member.
# Dino ownership :
  • --- Tribe owned
  • --- Personally owned, Tribe ridden
  • *** Personally owned, personally ridden.
  • ^ Meaning any dino must be tamed by the player and is from then owned by the player and cannot be loaned or stolen by another member.
# Structure ownership :
  • --- Tribe owned
  • --- Personally owned, Tribe Snap, Admin Demolish
  • *** Personally owned, personal snap.
  • ^ This one is alternative of two choices, maybe "admin demolish" could be the alternative. However idea is, player build, own and can lock down his own property.
# Locks & Pincodes :
  • --- Tribe Locks & pincodes
  • *** Person locks & Pincodes
  • ^ Again, each player have their own doors, lockers etc and everything is private to that player.

Idea is to avoid anyone borrowing another tribe members dinos, or loan huge amounts of resources from a locker, without the consent of another player.

Players who choose to share their pincode with another player can of course do so, and with that the other player(s) can access their lockers.



Miscellaneous :

To get maximum safety it is suggested that players build within close distance of the server tribe headquarter rather than opposite side of the map. It is still up to each player where to build, aslong as they follow the rules as stated in the server ruleset.

To minimize the workload on admin, and clutter on the map etc, vacant buildings will be destroyed as in stated in the ruleset. At same time any dino will be destroyed too, unless tribe members should request them. There will be no more "dino garage" as it takes way too much management time (transport, feeding etc).


The core idea is that everyone in the tribe help each other as much as possible to create a strong active tribe that can hold up if theres a pvp battle.

By helping out it means that if someone have a tamed mammoth that can harvest wood then please use it to harvest some for the tribe members aswell, while the one with doedicurus can supply some extra stones for those in need.


As idea mature this post will be revised again, comments & feedback is ofc welcome.




---> Original idea.

Briefly this been discussed on the PvE server earlier :

Server managed tribes A & B (name will ofc be something different).

Tribe A would be the highly active players.
Tribe B would be the more casual players.

Exact governance settings per tribe would be to determined ofc.

I suggest reading this link to get an idea of tribe governance settings possible.


The idea behind this is that new players can join tribe B to begin with, to learn the game, get some help, have a social community around them etc.

Then later on, if their very active can move on to tribe A.

Tribe A & B would of course not be in conflict but supporting each other as needed.


Feel free to discuss this, or alternatives etc.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)