arwarld/logd-sharped

Legend of the Green Dragon - Clone with C#

logd-sharped's Issues

Write library-functonality

Include all needed functionality from theese files.

• addnews.php
• arraytourl.php
• arrayutil.php
• battle-buffs.php
• battle-skills.php
• bell_rand.php
• buffs.php
• censor.php
• charcleanup.php
• checkban.php
• commentary.php
• constants.php
• creatures.php
• datacache.php
• datetime.php
• debuglog.php
• dhms.php
• dump_item.php
• errorhandler.php
• errorhandling.php
• events.php
• experience.php
• expire_chars.php
• extended-battle.php
• e_dom.php
• e_rand.php
• fightnav.php
• forcednavigation.php
• forest.php
• forestoutcomes.php
• forms.php
• gamelog.php
• holiday_texts.php
• http.php
• increment_specialty.php
• is_email.php
• local_config.php
• lookup_user.php
• mail.php
• modules.php
• motd.php
• mountname.php
• mounts.php
• names.php
• nltoappon.php
• output.php
• output_array.php
• pageparts.php
• partner.php
• php_generic_environment.php
• pullurl.php
• pvplist.php
• pvpsupport.php
• pvpwarning.php
• redirect.php
• register_global.php
• safeescape.php
• sanitize.php
• saveuser.php
• settings.php
• showform.php
• show_backtrace.php
• source.php
• spell.php
• sql.php
• stripslashes_deep.php
• substitute.php
• superusernav.php
• su_access.php
• systemmail.php
• tabledescriptor.php
• taunt.php
• template.php
• tempstat.php
• titles.php
• translator.php
• villagenav.php

Custom max level

Make the module-'interface'

Should be something like this:

• Abstract module-class every module inherits
• Every module gets its own project with the dependency of LoGD-Core
• Since its its own project every module gets its own *.dll-file
• The (probably) GameMaster-object detects every *.dll in the /Module directory of its running path
• The module manager accesses the properties, methods of the module-*.dll via assembly loads.
• Installation and de-installation, activation and de-activation, is done within the module-*.dll

Write table definitions and element classes

Tables todo:

• accounts
• accounts_output
• armor
• bans
• clans
• commentary
• companions
• creatures
• debuglog
• faillog
• gamelog
• logdnet
• logdnetbans
• mail
• masters
• moderatedcomments
• modules
• module_event_hooks
• module_hooks
• module_objprefs
• module_settings
• module_userprefs
• motd
• mounts
• nastywords
• news
• paylog
• petitions
• pollresults
• referers
• settings
• taunts
• titles
• translations
• untranslated
• weapons

Create scenes for all accessible .php-files

Write scenes for all default (builtin) Pages

• about.php
• armor.php
• armoreditor.php
• badword.php
• bank.php
• battle.php
• bio.php
• bios.php
• clan.php
• common.php
• companions.php
• configuration.php
• create.php
• creatures.php
• donators.php
• dragon.php
• forest.php
• gamelog.php
• gardens.php
• graveyard.php
• gypsy.php
• healer.php
• hof.php
• home.php
• inn.php
• list.php
• lodge.php
• logdnet.php
• login.php
• mail.php
• masters.php
• mercenarycamp.php
• moderate.php
• modules.php
• motd.php
• mounts.php
• newday.php
• news.php
• paylog.php
• payment.php
• petition.php
• prefs.php
• pvp.php
• rawsql.php
• referers.php
• referral.php
• rock.php
• shades.php
• source.php
• stables.php
• stats.php
• superuser.php
• taunt.php
• titleedit.php
• train.php
• translatortool.php
• tree.txt
• untranslated.php
• user.php
• viewpetition.php
• village.php
• weaponeditor.php
• weapons.php

Write DB wrapper class

Write a wrapper for the database connection.

On initialization: Load the entire database into a fitting builtin data-structure
On data-request: Serve data already leaded from the SQL-database
On data-update: Update the SQL, on success also update the builtin-data
On shutdown or program-crash all verified (user-presented) data is already in SQL-database

Things to concern:
All operations shoud be thread safe.