Closed GregHib closed 4 years ago
Will content need a dependency on the engine?
Naming conventions. Should packages have a strict no plurals rule?
https://softwareengineering.stackexchange.com/a/75929/352855
Use the plural for packages with homogeneous contents and the singular for packages with heterogeneous contents.
com.myproject.task.TaskCollection
com.myproject.task.Task
com.myproject.task.TaskHandler
com.myproject.task.TaskFactory
com.myproject.tasks.TakeOutGarbageTask
com.myproject.tasks.DoTheDishesTask
new structure including the majority of potential future features
content
interaction
item
floor item
spell
object
mob
player/bot
widget
transport
teleport
shortcut
fairy ring
community
assist
clan
friend
trade
eco
shop
exchange
activity
achievement
quest
free
novice
intermediate
experienced
member
mini
novice
intermediate
experienced
master
grandmaster
special
diversion
time
daily
weekly
monthly
random
item
trail
holiday
skill
gather
combat
support
artisan
combat
boss
core
client
update
network
handlers
camera
entity
player
bot
mob
item
object
world
region
map
land
movement
collision
widget
dialogue
task
deferrals
script
engine
artemis
bag
dsl
event
game
archetypes
plugin
task
defer
instance
right/privilege
timer
attribute
network
client
world
service/data/model
cache
definition
save
database
api
model
components
events
archetypes
logic
systems
?
engine
core
content
Ideal architecture being:
Network
handlers
should be inengine
but this will mean some communication will be needed for e.g player count to send to social-server for worlds, and classes such asSyncStage
andUpdateBlock
to stay inside the engine.Originally posted by @GregHib in https://github.com/hestia-rsps/hestia/issues/32#issuecomment-561888769
List exactly what needs migrating from engine -> core and core -> plugins beforehand to get a sense of what effect these changes will have.