Skip to content
This repository was archived by the owner on Aug 12, 2025. It is now read-only.

M1L4/QuestingDebug

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

130 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

  • Last Update:
    • 2017 09 14
    • 13:06 CEST (UTC +1)
  • CommitID: 20
  • CommitLog:
  [tag] 
  - finalized kanto release
  • Branch: Master

  • Characteristics:

    • most recent bugfixes
    • most stable version
    • no features of branches
  • new: Branch/Feature BikeQuest integrated, therefore branch will probably be removed in time. Still have to read gits specifc workflow/-process to know, whether it should stay as it is or be removed.

Hi everyone,

[introduction]

this is a questing fork, with the intention to improve, expedite and update the master version to new hights. So see this as a beta version of the next Questing update. The original project owner is still wiwi and as such, all released versions will be found in his project: https://github.com/WiWi33/Questing.lua.

As it didn't get any attention lately, Questing contains open problems that prevent it from functioning - I'll try to make it work again as fast as possible.

My current priority list:

  1. mandatory fixes
  2. some appointed features

For the time being I don't intend add:

  1. new functionallity
  2. new content

[pointers]

  • [branches] As I am developing multiple features at times, multiple branches will exist. Feel free to debug test any of them. And give me feedback. They can be found, when clicking the branch button top left over the current project.
  • [issues] When encountering one use githubs issue system:
    • Title Format: I would prefer: "banchName | shortIssueDescription". This is due to the fact, that I couldn't find any options for branch correlating related issue tagging.
    • Quest: pls provide running quest - this looks like [00:11:05] Starting new quest: Sould Badge: Fuchsia City
    • Logs: add any form of log, you think could help narrowing down the error source. E.g.: Debug or normal textbox prints. Post them if unsure.
    • Detail: Provide as detailed as possible/willing. Details help a lot, when debugging.

Side Note: the more information (people using minus people that actually provide some) I/we get, the better it is for identifying the error. Help me to help us all :)

Nice botting everyone ;)

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Lua 100.0%